Lists Home |
Date Index |
- From: "Don Park" <firstname.lastname@example.org>
- To: "David Megginson" <email@example.com>, "xml-dev Mailing List" <firstname.lastname@example.org>
- Date: Tue, 24 Feb 1998 17:55:24 -0800
>The last five methods are much more of a problem, and I'm still
>agonizing over what to do. Why do we have binary entities in XML at
>all? Is anyone going to use them, or will everything be done with
>Attributes are the _only_ way to get at binary entities in XML, so if
>I don't provide some way to get access to them here, then SAX parsers
>and applications make it impossible to use binary (NDATA) entities at
>all. I am very reluctant to create a new class or interface just for
>entities (and yet another for notations), when other types of objects
>do not have their own classes, and I certainly don't want to re-invent
>(or pre-invent) the DOM.
How about replacing the five with following method and three constants?
public static final int NAME = 0;
public static final int PUBLIC_ID = 1;
public static final int SYSTEM_ID = 2;
public abstract String getDataInfo (int index);
Since AttributeList is valid only within startElement method, you can reuse
a single string array rather allocate a new one per getEntityInfo method.
If the method returns null, then it is attribute has no info.
If you haven't guessed by now, the constants above are used to index into
the returned array. Implementations should take steps to make sure the size
of the returned array is 3 and stuff null for NAME if it is not a notation.
Does this help?
>David Megginson email@example.com
>Microstar Software Ltd. firstname.lastname@example.org
>xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
>Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
>To (un)subscribe, mailto:firstname.lastname@example.org the following message;
>To subscribe to the digests, mailto:email@example.com the following
>List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)