OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: deterministic content model?



[Rob Lugt]

>
> The reason for this dichotomy is that XML processors are not required to
> analyse the content model to see if it is deterministic *unless* the
> instance document contains an element of that type.  This is my
> understanding of xml 1.0, 3.2.1 [1] which reads:-
>
> "For compatibility, it is an error if an element in the document can match
> more than one occurrence of an element type in the content model."
>

I have to ask, though, is that section written precisely or not?  I take it
as meaning this:

        For compatibility, it is an error if an element in A document COULD
match
        more than one occurrence of an element type in the content model."

If this is the correct reading, then the non-deterministic evaluation is
made across the set of all possible documents, not just the instance
document in question.  To me, this makes much more sense, since the
acceptablility of a content model is decoupled from any one instance.

Does anyone definitely know whether this is just an editorial issue (my
reading) or whether Rob's reading is what was intended?

Cheers,

Tom P