Unify document loading in Context Processing?

[helins]

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.1 details how resolving the context string against base URL might fail ; 5.6.3 does not mention anything about failure when resolving the value of @import against base URL
• 5.2.4 is very explicit about not dereferencing a URL that has already been dereferenced ; 5.6.4 goes straight into dereferencing without any further consideration

[gkellogg]

5.6.5 says what to do if loading the document fails; this would include cases where the URL is invalid.

5.2.4 is explicit about not dereferencing again, due to potential recursion loops. I don't think that the @import case had the same concern (@dlongley may recall), but implementations are generally encouraged to cache the result of retrieving external documents, which could be considered an expected optimization.

[helins]

Thanks @gkellogg. I guess not but would it make sense at all to also replicate 5.2.3 in 6, WRT to remote contexts?