foaf:Organization has been replaced by foaf:Agent in draft 2 v0.03 and now all other properties defined by FOAF for foaf:Agent can be used as optional properties. So a receiver MUST be able to handle the information for all that 19 new optional properties. (There was no one at the previous report with foaf:Organization)
Do we really want that? As most of that properties may be useless from a Data Catalog perspective, do we really want to include that sort of overload to those who want to develope DCAT AP compliant receivers?
Proposal is not to include any optional property for Agent or define a core subset of those at foaf:Agent as optional properties.
Component
DocumentationCategory
improvement
Login or
create an account to comment.
Comments
I see two other options:
1. include in section 6 only the classes defined by DCAT, i.e CatalogRecord, Catalog, Dataset and Distribution and remain silent on the 'external' classes skos:Concept, skos:ConceptScheme and foaf:Agent.
2. remove the sections on optional properties for the 'external' classes and only specify the mandatory properties.
For the time being, I am deleting the sections mentioning optional properties for these classes. It is still possible for communicating partners to exchange more information about instances of those classes but there are no obligations above and beyond the mandatory properties.
Included in draft 3.