The practical relevance of CPOV with respect to the W3C ontology of organizations is that it introduces some useful attributes and associations, such as hasContactPoint, logo, and address. However, in…
In the documentation of CPOV V1.0.0 and in the UML diagram, cpov:PublicOrganization is defined as a subclass of org:Organization. However, in the associated RDF file (cpov_rdf_schema_turtle_v0.03.ttl)…
We have described the class org:OrganizationalUnit as a subclass of cpov:PublicOrganization. We have done so implicitly in the text and declaratively in the diagram. In the text we write: "An…
Dear all, I find it worrying that terms specifically selected/optimized for annotating web pages for SEO and SERP are recommended in a core vocabulary. A core vocabulary by its definition should be…
Section 4.1.13 and 4.1.14 mention that the range of contactPoint is a VCard. They also mention that the rdf binding of contactPoint is schema:contactPoint. However, schema.org defines contactPoint as…
Moreover (continuing on issue "CPOV: Property CPOV:Temporal missing."): temporal availability can vary according through which channel the PublicOrganisation is contacted (eg from 8-19u by telephone…
A property CPOV:PublicOrganisation:Temporal comparable to CPSVAP: PublicService:Temporal or CPSVAP: PublicService:Channel:Availability should be added. Useful where the availability of the…
I do not understand the purpose of letting adminUnit Level 2 information preceeding adminUnit Level 1 in the UML diagramm.
Is this intentionally or a small diagramm mistake?
BTW: in other core…
What level of detail does the WG expect concerning vocabularies defined elsewhere? (things like the Core Public Organisation and Location vocs). PROPOSAL: Just cite the properties that are mandatory…
There is a linked data API, which uses an extension of W3C Organization ontology to expose representation rights (e.g. who and in which conditions is eligible for signing a contract on behalf of an…
We should be aware of what the boundaries are of the CPOV? Last meeting went also about roles/mandates and if they should be included within the core. Maybe the scheme included could help guide the…
The domain of dcat:contactPoint is dcat:Dataset. An org:FormalOrganization is neither owl:sameAs nor a subclass of dcat:Dataset, so the use of this property is inconsistent. See https://www.w3.org/TR…
