Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine roles and role descriptions for profile resources #788

Open
rob-metalinkage opened this Issue Mar 5, 2019 · 4 comments

Comments

Projects
None yet
4 participants
@rob-metalinkage
Copy link
Contributor

rob-metalinkage commented Mar 5, 2019

Here are the current ideas for roles. In TTL as this is a compact form for the different parts of each definition

:aggregatedConstraints a owl:NamedIndividual,
skos:Concept,
prof:ResourceRole ;
skos:broader :fullConstraints ;
skos:definition "Full Constraints not only for this Profile but also for all dependencies (Profiles or dct:Standards)"@en ;
skos:usageNote "Use this Role when you want to provide a resource that validates data according to this profile and also its dependents. You must include the Full Constraints of all dependencies within this resource" ;
skos:prefLabel "Aggregated Constraints"@en .

:codeRepository a owl:NamedIndividual,
skos:Concept,
prof:ResourceRole ;
skos:definition "Repository for source code and profile artifacts"@en ;
skos:prefLabel "Code repository"@en ;
skos:topConceptOf : .

:extensionConstraints a owl:NamedIndividual,
skos:Concept,
prof:ResourceRole ;
skos:broader :partConstraints ;
skos:definition "Constraints implemented by this Profile building on dependencies but not including them"@en ;
skos:usageNote "Use this Role when you want to provide a resource that validates data according to this profile but only in so far as it is a constraint on its dependents. Therefore, this resource must not also include any dependents' constraints" ;
skos:prefLabel "Extension Constraints"@en .

:fullConstraints a owl:NamedIndividual,
skos:Concept,
prof:ResourceRole ;
skos:definition "Complete set of constraints for a profile"@en ;
skos:prefLabel "Full Constraints"@en ;
skos:topConceptOf : .

:guidance a owl:NamedIndividual,
skos:Concept,
prof:ResourceRole ;
skos:definition "Guidance notes of profile"@en ;
skos:prefLabel "Guidance"@en ;
skos:topConceptOf : .

:partConstraints a owl:NamedIndividual,
skos:Concept,
prof:ResourceRole ;
skos:definition "Partial set of constraints for a profile"@en ;
skos:prefLabel "Part Constraints"@en ;
skos:topConceptOf : .

:specification a owl:NamedIndividual,
skos:Concept,
prof:ResourceRole ;
skos:definition "Reference document which describes the standard"@en ;
skos:prefLabel "Specification document"@en ;
skos:topConceptOf : .

:vocabulary a owl:NamedIndividual,
skos:Concept,
prof:ResourceRole ;
skos:definition "Machine readable definition of a vocabulary or schema. Typically expressed in RDF, XSD, UML DDL, Table Schema or similar"@en ;
skos:prefLabel "Vocabulary"@en ;
skos:topConceptOf : .

@rob-metalinkage

This comment has been minimized.

Copy link
Contributor Author

rob-metalinkage commented Mar 5, 2019

I think we should simplify and prioritise these - here is a straw man

:specification - human readable definition of the profile
:guidance
:constraints - constraints specific to the profile
:validation - provides validation resource for the profile (implies inclusion or import of inherited constraints)
:structure (schema?) - provides a machine readable structural description of a profile - such as a schema or shape
:mapping - provides a mapping between two specifications
(could add :mappingTo and :mappingFrom properties to indciate both target and direction)
:vocabulary - provides definitions for terms used in the profile specification

note i think subtleties about aggregation etc can be left to extensions

@makxdekkers

This comment has been minimized.

Copy link
Contributor

makxdekkers commented Mar 6, 2019

Can I again make a comment about circular definitions? Saying that 'constraints' are 'constraints' or that 'validation' 'provides validation resource' or that 'mapping' 'provides a mapping' is not really helpful for someone who does not have the right background. Also, the use of 'provides' in the definition should be avoided -- it's much better to just state what it is rather than what it does.
E.g.
'constraint': description of obligations, limitations or restrictions that apply to the profile
'validation': instructions to be used to verify conformance to the profile
'mapping': description of conversion between two specifications

@rob-metalinkage

This comment has been minimized.

Copy link
Contributor Author

rob-metalinkage commented Mar 13, 2019

Straw man list of roles and descriptions merged into current WD. closing this issue - open new ones about specific roles as required.

@kcoyle

This comment has been minimized.

Copy link
Contributor

kcoyle commented Mar 13, 2019

Strawman list of roles is not "determine roles".

@kcoyle kcoyle reopened this Mar 13, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.