would it be possible to reserve @view for JSON-LD v.next
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 139
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Hopefully this is the right place to post this topic:
JSON-LD provides a declarative data model for use on the web. However there is no generic way to view that data, by introspecting on it
I had the idea of a @view keyword, which could live at the same level as the @context
It would simply pull in a module that is used to view the data
This could make for some compelling demos where data becomes self displaying
The proposal is simply to reserve the keyword for future exploration
I would imagine @view occurring at the document level at most once, to begin with
It would be quite easy to create a shim that does this, making it possible to create attractive markup for much of the existing data in the JSON-LD ecosystem
This request goes beyond JSON-LD 1.1, to perhaps 2.x or future versions, expected to be some years from now
For now this proposal is simply to reserve the keyword as a place holder, while implementations can be created and then align
Would love to know any thoughts on this!
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
The issue names no files, tests, or implementation entry points. Start by reviewing the proposal to reserve a document-level @view keyword for a future JSON-LD version; done would require a resolved specification decision on whether and how the keyword is reserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100