Clarification: Example 45, expansion of interest.name
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 139
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
In Example 45, interest.name expands to http://schema.org/name despite interest having a property-scoped context with vocabulary set to http://xmlns.com/foaf/0.1 (and foaf defining a property name.)
Is this because the domain of foaf:interest is foaf:person and foaf:person is not in the domain of foaf:name, (but e.g. of foaf:first_name)? This seems illogical, since it requires the JSON-LD processor to understand RDF schema (at least), everything else up to now has been self-contained.
I think actually this is because @vocab acts as a fall back for terms not defined elsewhere (here name in the outer @context) but perhaps a notice would be helpful.
Contributor guide
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 Example 45 in the linked JSON-LD Syntax specification and trace how interest.name is expanded using the outer and property-scoped contexts. Clarify the fallback behavior for @vocab and explain why RDF schema domain information is not required; done means the example or surrounding text answers the reported question.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100