Field names in resource-wide metadata vs string-level metadata
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 16
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
string-meta recommends language and direction for resource-wide metadata, but lang and dir for string-level metadata.
The reason might be those names mapping directly to HTML attributes when a consumer renders the string. But that is a convenience mapping, not a data-model requirement.
Should we use language and direction consistently for metadata fields, and use lang and dir only in markup 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 reading the linked W3C sections on the document language default and single linguistic field. Compare the resource-wide and string-level metadata names with the issue’s distinction between data-model fields and HTML attribute mappings. Done means reaching and documenting a decision about consistent field names, including which names remain in markup examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100