Murata-san
>I am very confused. First, can entity renaming as specified in Part8
handle renaming of unparsed entities? This should be very clearly
stated. If it is covered, the definition in 3.2 is confusing, since
it says "general".
Good hit. I had not reviewed the definition there in the light of the switch
to DOM. The restriction has been removed.
>> The XDM model specifically states:
>> Because the data model requires that all general entities be expanded,
there
>> will never be unexpanded entity reference information item children.
>> Therefore XDM cannot be used as the data model for DSRL processing any
more
>> than the XML Information Set can.
>Please very clearly state this in the beginning of this part!
As Clause 4 makes no reference to XSLT 2.0 I see no reason for mentioning
XDM there.
>Yes, this is highly confusing to me. Since Annex B relies on XSLT2, I
immediately started to look for the definition of entities in XDM.
>I do not believe that XML parsers are obliged to provide replacement
texts for all parsed entities.
True
>>>It should be made
>>> clear that internal parsed entities are also outside the scope of DSRL.
>> Why? If the DOM records them why cannot they be referred to and
processed?
>You restrict the scope of this part to those XML parsers which handle DOM
Level 3
streams. DSRL as defined in this part per se cannot be implemented on those
XML
parsers which handle the other data models such as XDM or the XML
Information Set. This limitation should be very clearly stated in the
beginning of this part.
I have changed the wording to make this, I trust, clearer
>However, even when we impose this very severe limitation, the DOM does
not always record entity references. Dom Level 3 Core clearly say
>"Moreover, the XML processor may completely expand references to
entities while building the Document, instead of providing
EntityReference nodes"
>Thus, DSRL is implementable on only thowse XML parsers which
handle DOM Level 3 streams, preserve entity references, and provide
replacement text for entities. Which XML parser satisfies these
requirements??
Why do you insist on it being an XML parser that processes DSRL? I see no
reason to impose any such restriction. Any XML processor that understands
the XML naming rules, and can identify entity references and their
replacement text, should be permitted to carry out DSRL processing.
>First, it should be clearly stated that "Entity" in your text mentions
an interface "Entity" as defined in Dom Level 2 and 3. Without this
clearification, this text is meaningless.
I have added a definition of entity node to section 3 to clarify this
imported term, even though it is in a note rather than normative text.
>I would still argue that all XML parsers expand references to internal
parse entities and that no DOM level 3 streams preserve such references.
In that case how did I manage to process entity nodes using Saxon?
>In my opinion, the first sentence in the above quotation justifies my
interpretation.
I beg to differ, most strongly. The phrase "XML does not mandate that a
non-validating XML processor read and process entity declarations made in
the external subset or declared in external parameter entities" specifically
states that a non-validating XML processor (note the terminology, not an XML
parser) need not process entity declarations.
>The contents of MappedEntities.ent created from the DSRL example in page
29 should be shown in Appendix B.
Good idea. Done.
> I would like to make entity renaming
and entity definitions of DSRL optional.
OK, done
>You can say that the processing model works only when the underlying XML
processors preserve entity references and provide replacement text for
all parsed entities.
Done
>As long as this complex situation is very clearly explained, I will not
ague agains the use of XSLT2 in this non-normative appendix.
Is the attached revision, which incorporates the changes note above, likely
to get approval from the Japanese National Body?
Martin
-- DSDL members discussion list To unsubscribe, please send a message with the command "unsubscribe" to dsdl-discuss-request@dsdl.org (mailto:dsdl-discuss-request@dsdl.org?Subject=unsubscribe)
This archive was generated by hypermail 2.1.8 : Mon Apr 30 2007 - 19:03:04 UTC