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

Property to link to the actual implementation artefacts in a profile description #362

Closed
dr-shorthair opened this issue Sep 20, 2018 · 0 comments
Labels
profiles-vocabulary For discussion of profile description vocabulary

Comments

@dr-shorthair
Copy link
Contributor

On the basis of a small test of the Profile Description ontology
https://github.com/w3c/dxwg/blob/profiledesc-examples-simon/profiledesc/examples/adms.ttl
I think we need a property to carry explicit links from the ImplResourceDesc (an association class) and the actual implementation resource.

I suggest calling this either pd:artefact or pd:implementationResource with the RDF definition

pd:artefact
  rdf:type owl:ObjectProperty ;
  rdfs:comment "The artefact (resource) linked to a profile through an Implementation Resource Descriptor" ;
  rdfs:domain pd:ImplResourceDesc ;
  rdfs:label "artefact (resource) " ;
  skos:editorialNote "A property to link from a pd:ImplResourceDesc to the actual implementation resource. " ;
.

Related to #323 and #355

@dr-shorthair dr-shorthair added the profiles-vocabulary For discussion of profile description vocabulary label Sep 20, 2018
@dr-shorthair dr-shorthair added this to To do in Profile Guidance via automation Sep 20, 2018
@dr-shorthair dr-shorthair changed the title Property to link to the actual implementation artefacts Property to link to the actual implementation artefacts in a profile description Sep 27, 2018
Profile Guidance automation moved this from To do to Done Dec 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
profiles-vocabulary For discussion of profile description vocabulary
Projects
Development

No branches or pull requests

1 participant