Core Public Organisation Vocabulary

Final Working Group meeting

17 November 2016

Opening, agenda, tour de table

Agenda

• Opening

• Tour de table

• Objectives

• Discussion of open issues

• Next steps

• Closing

Tour de table

Objectives

Objectives

• Discuss and agree on the resolution of the issues created based on the comments received during the public review period.

• Define next steps and finalise the CPOV specification.

Discussion of open issues

1. schema.org properties recommend as RDF terms

1. Link: https://joinup.ec.europa.eu/node/156652

2. Issue: Specific terms are recommended in the core vocabulary which should be broadly applicable.

3. Proposal:o Add recommended terms for both general purposes and annotation of web

pages for each property and class.

4. Proposed resolution:o Reject proposal.

o Schema.org is now well established, managed and used. Where the needs of a Core Vocabulary are met by schema.org, we get the added bonus of greater discoverability.

Proposed changes

2. Property CPOV:Temporal missing

1. Link: https://joinup.ec.europa.eu/node/156581

2. Issue: The property CPOV:Temporal is missing

3. Proposal:o Create a new property CPOV:PublicOrganisation:Temporal.

4. Proposed resolution:o Reject proposal.

o Spatial property for an organisation is the area over which the PO operates, not its location (address). If we were to include a temporal property analogous to the spatial one, it would mean that the public organisation only had legal force during that period. However, including opening hours to the model can be a possibility.

o The ContactPoint class is the place for opening hours.

Proposed changes

3. Range of contactPoint is not VCard

1. Link: https://joinup.ec.europa.eu/node/156615

2. Issue: Section 4.1.13 and 4.1.14 mention that the range of contactPoint is a Vcard and that the RDF binding contactPoint is schema:contactPoint. However, schema.org defines contactPoint as having range schema:ContactPoint. The semantics of both should not be the same entity.

3. Proposal:o Change the range to schema:ContactPoint

4. Proposed resolution:o Accept proposal.

o Change the range etc. See new section 4.5

Proposed changes

4. Property hasSubOrganization is bound to org:hasSubOrganization and not property subOrganization bound to org:SubOrganization

1. Issue: in section 4.1.10, the property subOrganization is bound to org:subOrganization and subOrganizationOf is bound to org:subOrganizationOf. Problem is that in the specification of the organization ontology org:subOrganization does not exist.

2. Proposal:o Change the org:subOrganization by org:hasSubOrganization.

3. Proposed resolution:o Accept proposal.

o Change the property.

o (Done in previous version)

Proposed changes

5. Misleading description of org:OrganizationalUnit

1. Issue: The class org:OrganizationalUnit was described as a subclass of cpov:PublicOrganization, implicitly in the text and declaratively in the diagram. In the diagram, there is a generalization between the OrganizationalUnit and the PublicOrganization and the textual description can be interpreted as a confirmation.

2. Proposal:o Make the textual description more precise

o Move the generalization symbol in diagram to show that org:OrganizationalUnitis a subclass of org:Organization as defined in Organizational Ontology.

3. Proposed resolution:o Accept proposal.

o Change the description and the diagram.

Proposed changes

Next steps

• Finalise the CPOV specification by addressing the received comments from today’s call.

• Publish the specification on Joinup in December.

Further work

Share your ideas!

ISA² programmeYou click, we link

http://ec.europa.eu/isaISA@ec.europa.eu

@EU_ISA2

Unit B6, Directorate-General for Informatics,

European Commission, Brussels

Promoting semantic interoperability in Europe

Join the SEMIC group on LinkedIn

Follow @SEMICeu on Twitter

Join the SEMIC community on Joinup

Project Officers Vassilios.Peristeras@ec.europa.eu

Athanasios.Karalopoulos@ec.europa.eu

Get involvedVisit our initiatives