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

dpv-legal docs do not contain properties and their info #41

Closed
coolharsh55 opened this issue Jun 15, 2022 · 2 comments
Closed

dpv-legal docs do not contain properties and their info #41

coolharsh55 opened this issue Jun 15, 2022 · 2 comments
Milestone

Comments

@coolharsh55
Copy link
Collaborator

The DPV-LEGAL extension contains properties associated with ISO country labels which are not present in the HTML documentation. The use of these properties, e.g. to indicate ISO label for a specific country, is also not present in the tables for that concept. Both of these should be added in. This needs to be done within the template, e.g. https://github.com/w3c/dpv/blob/master/documentation-generator/jinja2_resources/template_dpv_legal.jinja2

@coolharsh55
Copy link
Collaborator Author

Relevant for #37

@coolharsh55 coolharsh55 added this to the DPV v1 milestone Jun 30, 2022
coolharsh55 added a commit that referenced this issue Jul 2, 2022
Adds appropriate property domain/range for each of the semantics in DPV
(Core, RDFS+SKOS, OWL) in the HTML documentation. This information was
already present in the RDF files, so they did not require any changes.
Where something was not provided, the string 'unspecified' is presented
in documentation.
@coolharsh55
Copy link
Collaborator Author

The documentation does not include properties used for country codes, e,g. iso_alpha2, though these are defined in the serialisations. These should be added to the HTML documentation tables for each concept.

coolharsh55 added a commit that referenced this issue Aug 17, 2022
Adds appropriate property domain/range for each of the semantics in DPV
(Core, RDFS+SKOS, OWL) in the HTML documentation. This information was
already present in the RDF files, so they did not require any changes.
Where something was not provided, the string 'unspecified' is presented
in documentation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant