language-maps don't allow separate base direction
Open
Nobody has claimed this yet.
defer-future-version
- Dominant language
- HTML
- Stars
- 139
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Language Maps allow strings to be indexed by their language-tag, which provides no means of changing the default or term-specific @direction.
A hypothetical change would be to allow value objects without @type or @language as the value of a language map.
{
"@context": {
"@version": 1.1,
"ex:lm": {"@container": "@language"}
},
"ex:lm": {
"en": "HTML and CSS: Design and Build Websites",
"ar-EG": "HTML و CSS: تصميم و إنشاء مواقع الويب"
}
}
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 issue #280 and the JSON-LD 1.1 language-map proposal, focusing on the suggested value objects without @type or @language. Determine the required processing and specification changes for separate default and term-specific @direction, then define compatibility expectations before implementation.
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
- 35/100