solid / solid/data-interoperability-panel
Inconsistent values for an Access Need's `accessNecessity`
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
The specification's class and shape definition defines possible values for accessNecessity as one of interop:AccessRequired or interop:AccessOptional. In Figure 13's linked example however, interop:accessRequired is used (lowercase "a").
I assume the linked example just contains a typo. Have not checked if the same thing happens in other examples.
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 comparing the AccessNeed definitions in the specification with the linked Figure 13 example at specification/snippets/projectron.example/needs.ttl. Check the other examples for the same capitalization and update any inconsistent accessNecessity value so it matches the defined AccessRequired or AccessOptional values.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100