Suggested new Roles

[nicholascar]

This Issue contains suggested additions to the Roles vocabulary.

[nicholascar]

SKOS Concept	role:manifest
Pref Label	Manifest
Definition	A schedule of profile content for a particular community or application.
Usage Note	...

[nicholascar]

SKOS Concept	role:executableRules
Pref Label	Executable Rules
Definition	A document containing machine-readable executable rules in a format indicated by a Media Type and/or conformance to a rules specification.
Usage Note	...

[nicholascar]

SKOS Concept	role:repository
Pref Label	Repository
Definition	A digital artifact repository used to store multiple artifacts. Likely to be a version control repository available online.
Usage Note	...

[nicholascar]

SKOS Concept	role:versionMapping
Pref Label	Version Mapping
Definition	A mapping between two versions of the same specification.
Usage Note	The vocabulary of version mapping relations (e.g. same, replaces, deprecated, similar etc.) should be indicated by use of prof:conformsTo on the mapping artifact to a versioning vocabulary or standard that it conforms to.
Example	...
Broader	role:mapping

[kcoyle]

Manifest: A schedule of profile content for a particular community or application.

I'm not sure what a list of profile content would be. Are you referring to a list of profile terms? Is this the definition of the profile in list form? Also, I generally think of manifests as being supplementary - like a list of things in a box would be a manifest. In essence, PROF itself is a manifest.

[rob-metalinkage]

I agree that PROF itself is functionally a manifest. So this would imply prof descriptions should self-reference using this role dct:conformsTo .

Its time to revisit both the governance of the roles vocab and the definitions now we have significantly more implementation experience. Its only short, and can be the focus of a targetted discussion.

[nicholascar]

SKOS Concept	role:template
Pref Label	Template
Definition	A resource having a preset format, used as a starting point by profile users to create final data instances likely to conform to the profile.
Broader	role:example

[nicholascar]

SKOS Concept	role:script
Pref Label	Script
Definition	Executable software that performs some action associated with use of the profile.
Narrower	role:validation

[nicholascar]

SKOS Concept	role:motivatingRequirements
Pref Label	Motivating Requirements
Definition	A collection of requirements that motivate the specification of this Standard
Scope Note	The specific form of the Motivating Requirements is left to the implementer - to be defined in a ResourceDescriptor instance - however the expectation is that individual requirements will be identified within the Motivating Requirements and this will allow linking of individual model elements in a specification (Classes, properties, axioms or similar constructs) to them.

[leskneebone]

A bit new to working on this, but I came to a similar conclusion, and jumped in head-first with a PR (now draft) to create PROF role concept "Catalogue" - which is perhaps a blend of the role:repository and role:manifest proposal.

I'll just add what prompted me to think about this: vocabularies. It's the vocabs that proliferate and, almost from a human spec readability point of view, a table indicting 10, 20... or even hundreds of vocabularies each with a separate statement is awkward. Perhaps that's more a page generation and layout problem, rather than a problem met with some kind of 'aggregated resource container' role. I do, however think that such a role is a nice touch-point between PROF and DCAT, the latter a key spec with regard to catalogue-type objects.