Following the kick off meeting, I have made changes to the concept model. As ever, this is intended as a dicussion point - what's missing that should be there, what's there that should be removed?
Starting from the Public Service class, we can see that there is an associated process that, new for this version, has inputs and outputs. These could be anything - documents, meetings, actions, life events.
As before, the process is subject to policies, plans and legislation. I've added in a new relationship "compliesWith" that can link a Process or a Service to a piece of legislation or a policy.
I've added in a target Community and the partOf/hasPart relationships to link services that include other services (these are Dublin Core terms). The (new) related relationship links any service to anotehr that is in some way related (more Dublin Core!).
Coverage/Extent is the Dublin Core class that covers temporal, spatial or jurisdictional restrictions on something. i.e. opening hours, area covered etc. DC provides the relevant properties and sub classes for this but doesn't expressly have a concept of something applying to an age bracket so this may not be a perfect fit but it looks pretty close and matches what we've used in other vocabularies. Coverage/Extent is very broad and can be specialised, for example, to a specific location (cf. INSIPRE Team's comments) and/or temporal (opening hours, seasonal availability etc. - cf. Muriel's comments).
I've removed the Agreement class.
An Agent can be a user or a provider, a group, organisation or individual. I've re-used the membership/role structure defined in the Organisation Ontology. The same ontology gives us the physical site(s) for a service to which contact information etc. can be added. The specialisation of ORG, the Registered Organisation Vocabulary, RegOrg, that began life here as the Core Business Vocabulary, provides the means to link registered businesses (cf. Fergal's comments).
Looking back over my notes from the meeting I think that's most of the comments covered. Do you agree? Two areas I'm not sure about:
- Periodicity, on demand etc. Does the coverage/extent class cover this or do we need something more specific?
- Service specification. My feeling is that the Process(es) and the (natural language) description might be sufficient. But it would be easy to add in a class of "service specification" if the WG felt it needed something specific to cover this?
Comments are very welcome.
Nature of documentation: Unpublished work