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

Prescription on the use of other vocabularies when creating a XKOS classification or correspondence table #69

Closed
laurentlefort opened this issue Feb 15, 2017 · 2 comments
Labels
Best practices Consider this issue for a "best practices" document

Comments

@laurentlefort
Copy link

Section 8 includes a number of recommendations on how to document an XKOS artefact (using annotation properties such as skosxl:label) but the non XKOS properties which can be used to annotate a classification are not listed in Table 1.
Would it be possible to add a listing of which properties are recommended for which types of XKOS (and SKOS) classes or a thematic one on the model of the one developed for the AgroPortal metadata: http://htmlpreview.github.io/?https://github.com/agroportal/documentation/blob/master/metadata/Metadata%20for%20AgroPortal.html

@laurentlefort
Copy link
Author

Section 8 includes a number of recommendations on how to document an XKOS artefact (using annotation properties such as skosxl:label) but the non XKOS properties which can be used to annotate a classification are not listed in Table 1.
Would it be possible to add a listing of which properties are recommended for which types of XKOS (and SKOS) classes or a thematic one on the model of the one developed for the AgroPortal metadata: http://htmlpreview.github.io/?https://github.com/agroportal/documentation/blob/master/metadata/Metadata%20for%20AgroPortal.html

@tfrancart
Copy link
Contributor

Example of description of statistical classifications in RDF will be provided in a Best Practice document.

@tfrancart tfrancart added the Best practices Consider this issue for a "best practices" document label Apr 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Best practices Consider this issue for a "best practices" document
Projects
None yet
Development

No branches or pull requests

2 participants