[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: unambiguity constraint
James Clark wrote: > Define a category to be ... Is this basically "single type" extended so that name classes can be handled correctly? Given a pattern, possibleElements enumerates all (URI-or-MAGIC, local-name-or-MAGIC) pairs for element names that occur within this pattern (Here I assume normalization is already performed). Even when such a pair occur in <not> or the second operand of <difference>, it is (correctly) enumerated. You did not mention <ref> in your algorithm. How do you handle it? Cheers, Makoto
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC