[Bug 2619] Complexity of precedence rules for "scope" (or "selectors")

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2619





------- Additional Comments From fsasaki@w3.org  2006-01-08 04:42 -------
(In reply to comment #1)
> Using one could have a rule saying "use only dislocated" or "use only inline 
> scope" would not really solve the issue: If a document has both notations the 
> tool will *have to* handle both, otherwise it would not be able to cover what 
> the document author wants.
Maybe we should make the behavior of ITS processing clearer, writing s.t. like
"first read the schema and look for ITS information, than the document (looking
for dislocated, than the document (looking for in situ)." This is what the
precedence order says anyway, but it might be useful to have it formulated
different.

Received on Sunday, 8 January 2006 04:42:08 UTC