Unify document loading in Context Processing?
Open
Nobody has claimed this yet.
Editorial
editorial:class 2
ErratumRaised
spec:editorial
- Dominant language
- HTML
- Stars
- 106
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
The Context Processing Algorithm deals with dereferencing remote documents at 2 occasions: 5.2 and 5.6. Both look very similar to the point where I do not understand why there are seemingly differences:
5.2.1details how resolving thecontextstring againstbase URLmight fail ;5.6.3does not mention anything about failure when resolving the value of@importagainstbase URL5.2.4is very explicit about not dereferencing a URL that has already been dereferenced ;5.6.4goes straight into dereferencing without any further consideration
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 comparing sections 5.2 and 5.6 of the Context Processing Algorithm, especially steps 5.2.1, 5.2.4, 5.6.3, and 5.6.4. Determine whether remote document resolution failures and already-dereferenced URLs should be described consistently, then update the specification so the two loading paths have aligned, explicit behavior.
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
- Mostly clear
- Newbie friendliness
- 35/100