Advanced search
Many associations defined for PublicOrganization should actually be moved to Organisation
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 the present CPOV version, these associations are attached to cpov:PublicOrganization, while they…
DISCUSSIONCreated: 15/03/2017Updated Date: 15/03/2017
cpov:PublicOrganization not a subclass of org:Organization in the RDF encoding
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) cpov:PublicOrganization is just defined as a subclass of dct:Agent. Suggested fix: change the rdf…
DISCUSSIONCreated: 15/03/2017Updated Date: 15/03/2017
Misleading description of org:OrganizationalUnit
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 Organizational Unit is a sub class of Public Organization [...]" ..which of course can be true and does not…
DISCUSSIONCreated: 16/11/2016Updated Date: 16/11/2016
Why are schema.org properties recommended as RDF terms?
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 broadly applicable... Understandably, the schema.org specification has a broad coverage, is made very…
DISCUSSIONCreated: 07/11/2016Updated Date: 07/11/2016
Range of contactPoint is not VCard
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 having range schema:ContactPoint. The semantics of both seem different enough to say that they…
DISCUSSIONCreated: 04/11/2016Updated Date: 04/11/2016
Temporal availability can vary with channel.
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, from 9-17u on-site). This is independent of the specific PublicServices that the PublicOrganisation…
DISCUSSIONCreated: 03/11/2016Updated Date: 03/11/2016
Property CPOV:Temporal missing.
A property CPOV:PublicOrganisation:Temporal comparable to CPSVAP: PublicService:Temporal or CPSVAP: PublicService:Channel:Availability should be added. Useful where the availability of the PublicService is not specific for the service but for the PublicOrganisation that provides it. Eg a…
DISCUSSIONCreated: 03/11/2016Updated Date: 03/11/2016
Address: AdminUnitL2 preceding AdminUnitL1 in diagramm?
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 vocabularies the ID as kind of unique key is shown first, here it is at the end. Component…
DISCUSSIONCreated: 23/09/2016Updated Date: 23/09/2016
Level of detail of referenced Core Vocs
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 for ther CPSV-AP Component Documentation Category feature
DISCUSSIONCreated: 21/04/2016Updated Date: 21/04/2016
Add a related solution
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 organization) of members of organizations. See https://developers.ir.ee/graph-api#get-all-data-of-an…
DISCUSSIONCreated: 15/03/2016Updated Date: 15/03/2016
Boundaries of the CPOV
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 discussion somewhat? IMHO I believe CPOV should be restricted to the upper right side of the scheme…
DISCUSSIONCreated: 09/03/2016Updated Date: 09/03/2016
Use of dcat:contactPoint
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/vocab-dcat/#Property:dataset_contactPoint Update: I'm unable to edit the issue title, but it would…
DISCUSSIONCreated: 01/03/2016Updated Date: 01/03/2016