Make Halyard vocabulary machine-readable
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 114
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
The Halyard vocabulary is currently available only in HTML. We can make it machine-readable by embedding structured data in RDFa into the HTML description. Some of it may become a part of the SPARQL Service Description of Halyard SPARQL endpoints.
I can have a go at this if it is found to be useful.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Halyard vocabulary HTML at https://merck.github.io/Halyard/ns and read the linked SPARQL Service Description specification. Determine which vocabulary terms should be represented as RDFa and which could belong in Halyard endpoint descriptions; done means the vocabulary is machine-readable and the intended service-description coverage is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100