Provider requirements In order to conform to the Core Public Service Vocabulary Application Profile any implementation MUST: Include at least all mandatory properties of all mandatory classes as indicated in “Detailed list of mandatory and optional classes and properties”; Include at least all mandatory properties of any optional class used for describing the Public Service, as indicated in list of mandatory and “Detailed optional classes and properties”; Not have more than one instance of properties that have 1 as maximum cardinality as specified in each subsection from Section 3.2 to Section 3.18; Define each property value according to the type specified in section 3 (see the UML diagram in Figure 2); Use the terms (classes and properties) in a way consistent with their semantics as declared in Section 3. A conforming implementation of the Core Public Service Vocabulary Application Profile may include classes and properties from other data models (vocabularies). In addition, a conforming implementation of the Core Public Service Vocabulary Application Profile may include terms from recommended controlled vocabularies for the corresponding properties, as listed in section 4. The Core Public Service Vocabulary Application Profile is technology-neutral and a publisher may use any of the defined in this document encoded in any technology although RDF and XML are preferred. Receiver requirements In order to conform to the Core Public Service Vocabulary Application Profile, any application that receives metadata MUST be able to: Process information for all classes specified in Section 3; Process information for all properties specified in Section 3. Process information for all controlled vocabularies specified in Section 4. "Processing" means that receivers must accept incoming data and transparently provide these data to applications and services. It does neither imply nor prescribe what applications and services finally do with the data (parse, convert, store, make searchable, display to users, etc.).
Provider requirements In order to conform to the Core Public Service Vocabulary Application Profile any implementation MUST: Include at least all mandatory properties of all mandatory classes as indicated in “Detailed list of mandatory and optional classes and properties”; Include at least all mandatory properties of any optional class used for describing the Public Service, as indicated in “Detailed list of mandatory and optional classes and properties”; Not have more than one instance of properties that have 1 as maximum cardinality as specified in each subsection from Section 3.2 to Section 3.18; Define each property value according to the type specified in section 3 (see the UML diagram in Figure 2); Use the terms (classes and properties) in a way consistent with their semantics as declared in Section 3. A conforming implementation of the Core Public Service Vocabulary Application Profile may include classes and properties from other data models (vocabularies). In addition, a conforming implementation of the Core Public Service Vocabulary Application Profile may include terms from recommended controlled vocabularies for the corresponding properties, as listed in section 4. The Core Public Service Vocabulary Application Profile is technology-neutral and a publisher may use any of the defined in this document encoded in any technology although RDF and XML are preferred. Receiver requirements In order to conform to the Core Public Service Vocabulary Application Profile, any application that receives metadata MUST be able to: Process information for all classes specified in Section 3; Process information for all properties specified in Section 3. Process information for all controlled vocabularies specified in Section 4. "Processing" means that receivers must accept incoming data and transparently provide these data to applications and services. It does neither imply nor prescribe what applications and services finally do with the data (parse, convert, store, make searchable, display to users, etc.).