W3C home > Mailing lists > Public > www-dom-ts@w3.org > January 2002

createEntityReference issues in DOM L1 test suite

From: Curt Arnold <carnold@houston.rr.com>
Date: Tue, 22 Jan 2002 00:48:22 -0600
Message-ID: <010001c1a310$c98f71f0$a800a8c0@CurtMicron>
To: <www-dom-ts@w3.org>
In off-list discussions with Dimitris, I mentioned that we still had not
received a resolution for the createEntityReference issue needed to complete
the L1 test suite.  I had mentioned a vaguely recalled message from David
Brownell, but had not been able to locate the appropriate message.  It
apparently was
http://lists.w3.org/Archives/Public/www-dom-ts/2001Nov/0055.html
 which discussed this issue in addition to the interpretation of "*" when
used as a namespace parameter.


>    Quite a number of the tests that try to verify behavior for
>    readonly nodes produce errors because instead of using
>   such nodes as found in the document, they try to create
>    new entity refs

Many of these tests intentionally use createEntityReference since the
read-only behavior would be untested when the processor or application
chooses to expand entity references.

>    ... such refs are created with no children.

They are in GNUJAXP, but not in Xerces-J.

>  (This is an area where IMO there are longstanding API
>   deficiencies in DOM.  First, you can't mark subtrees as
>   readonly.  Second, entities and entity refs, in their entirety.
>   I recall discussions late in DOM L1 to ensure it was legal
>   to never populate these nodes, yet these tests insist that they
>   must always be populated.)


From DOM L1 Core (Second Edition)
http://www.w3.org/TR/2000/WD-DOM-Level-1-20000929/level-one-core.html#ID-392
B75AE

>createEntityReference
>Creates an EntityReference object. In addition, if the referenced entity is
known,
>the child list of the EntityReference node is made the same as that
>of the corresponding Entity node.

All the entity definitions are in the internal subset so the sections that
allow external subset entity definitions to be ignored for non-validating
parsers should not apply.


----- Original Message -----
From: "Dimitris Dimitriadis" <dimitris@ontologicon.com>
To: "Ravi Kiran" <tr_kiran100@rediffmail.com>
Cc: <www-dom-ts@w3.org>
Sent: Monday, January 21, 2002 4:02 PM
Subject: Re: Parsing an XML from a String


> This list is devoted to the DOM Test Suite, and is therefore not the
> right forum for your question. Please send your inquiry to www-
> dom@w3.org, details on http://www.w3.org/DOM
>
> Thanks,
>
> /Dimitris
>
> On Thursday, January 17, 2002, at 06:24 , Ravi Kiran wrote:
>
> >
> > Somebody Answer this...
> >
> >    I want to parse an XML from a String. i.e., i have an XML obtained
> > in the form of a String and i want to parse it. How can i do that, as
> > the DocumentBuilder class has methods to parse from a File,
> > InputStream, InputSourse, etc, but not with a String. Please help me...
> >
> > Ravi.
> >
> >
>
Received on Tuesday, 22 January 2002 01:48:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 12:58:45 GMT