solid / solid/data-interoperability-panel
Add IRI for namespace in RDF serialisations
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Hi. The RDF files do not specify what is the IRI of the vocab in the file itself. e.g. interop.ttl does not specify namespace IRI in the prefix (<#>) or the vocabulary description (<>) or the definition of terms (rdfs:isDefinedBy <>). So once downloaded, there is no way to figure out what's the IRI. Though there is a prefix interop, it cannot be assumed to be the IRI.
PREFIX : <#>
PREFIX interop: <http://www.w3.org/ns/solid/interop#>
<>
dcterms:issued "2020-06-14"^^xsd:date ;
dcterms:modified "2020-09-24"^^xsd:date ;
rdfs:label "Terms for application interoperability in Solid"@en .
:Agent
a rdfs:Class ;
rdfs:comment "An agent profile for the Solid Ecosystem"@en ;
rdfs:isDefinedBy <> ;
rdfs:label "Agent"@en .
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 by inspecting interop.ttl and the other RDF serialisations described in the issue. Check how the namespace IRI is represented in each file, then update the serialisations so a downloaded file identifies its vocabulary and terms unambiguously. Done means the namespace IRI is present consistently in the relevant prefix, vocabulary description, or term definitions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100