solid / solid/data-interoperability-panel
Add a predicate to link `AccessDescriptionSet` with `AccessNeedGroupDescription` and `AccessNeedDescription`
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
This issue is very close to another one I pointed out regarding TypeIndexes.
There is no predicate linking a AccessDescriptionSet with AccessNeedGroupDescription and AccessNeedDescription.
So if you don't want to store all these resources on the same file (as it should be allowed, according to Linked Data philosophy), you have no way to find where they are.
IMO the spec should include a interop:hasAccessNeedGroupDescription and a interop:hasAccessNeedDescription predicates, which would be the reverse relationships of interop:inAccessDescriptionSet.
Another possibility could be to use the skos:member predicate. But since SKOS is not used elsewhere, it probably doesn't make much sense.
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 Access Description Set section of the linked Data Interoperability specification and compare it with the TypeIndexes issue referenced here. Determine whether the specification should define reverse predicates or use skos:member, then update the specification so the chosen relationship is explicit and resolves how separately stored descriptions can be discovered.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100