Now that DCAT AP draft_2_v0.03 allows properties from other specification than just DCAT (adms:contactPoint) that should be documented at section "1.2. Scope". Otherwise it may be confusing and contradictory with what is said at that section.
See also https://joinup.ec.europa.eu/asset/dcat_application_profile/issue/extens…
Component
DocumentationCategory
improvement
Login or
create an account to comment.
Comments
In Draft 3, I am changing the definition to:
An Application Profile is a specification that re-uses terms from one or more base standards, adding more specificity by identifying mandatory and optional elements to be used for a particular application, as well as recommendations for controlled vocabularies to be used.
That's good but I think not enough. The full 1.2 section focus currently solely on DCAT as the (apparently only) basis for the AP. If any other Vocabulary such as ADMS is being added then it should also be referenced there.
Modified text in section 1.2:
The Application Profile specified in this document is based on the Data Catalog Vocabulary (DCAT) specification[1] developed under the responsibility of the Government Linked Data Working Group[2] at W3C. DCAT is an RDF[3] vocabulary designed to facilitate interoperability between data catalogues published on the Web. Additional classes and properties from other well-known vocabularies are re-used where necessary.
[1] W3C. Data Catalog Vocabulary (DCAT). W3C Working Draft ,12 March 2013. http://www.w3.org/TR/2013/WD-vocab-dcat-20130312/.
[2] W3C. Government Linked Data (GLD) Working Group. http://www.w3.org/2011/gld/wiki/Main_Page
[3] W3C. Resource Description Framework (RDF). http://www.w3.org/RDF/
Included in draft 3.