Clarify language application and inheritance model
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 11
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
> Oh I see. Formally, Script Events do have a computed language regardless of whether they have an xml:lang attribute, and that might be inherited from the document level.
My view here is that we should go with the text in this pull request and if anyone asks about this subtlety we can consider amending or adding extra explanation.
Thanks, @nigelmegitt I think we should be clear about how language information is applied and inherited. From the class model (at least from what I can see) there is no other way to inherit the language information other than from the document level.
Originally posted by @andreastai in https://github.com/w3c/dapt/issues/181#issuecomment-1759172634
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 by reading the discussion in this issue and the referenced issue #181, then inspect the class model and document-level language rules mentioned in the thread. Done means the documentation clearly explains how language information is applied to Script Events and how it is inherited when no xml:lang attribute is present.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100