Andy Clark wrote :
> (-) Remove the Attribute Entity Information
>
> I would like to remove the methods for adding entity
> reference information from the XMLAttributes interface.
> I think that this information is redundant considering
> that we already store the non-normalized value of the
> attribute value. And we could provide a utility class
> that helps users break the attribute's value into its
> component parts.
>
> The inclusion of this data unnecessarily complicates
> the XMLAttributes interface and its use is limited. (At
> the moment, we don't use it at all. The idea was to be
> able to support the DOM's attribute nodes containing
> nested entity reference nodes. However, an attribute in
> the DOM doesn't take into account the non-normalized
> value; it only stores the normalized value and the
> entities only apply to the non-normalized value.)
>
If you are talking about removing all the entity related methods
from the XMLAttributes interface and adding utility classes instead,
it would be a good idea 'cause attributes donot have entity
references when we use a schema grammar.
> (+) Add Non-Normalized Value to Internal Entity Decl
>
> James Clark recently released a really cool tool that can
> read in a DTD and by analyzing the way parameter entities are
> nested within other parameter entities (and then used in
> content models), can output a RelaxNG grammar that separates
> the pieces appropriately. So I started thinking about if we
> could do the same thing in XNI.
>
I just looked into James Clark's code. The way parameter entities
are handled is neat.
> Earlier we re-arranged the XMLDTDContentModelHandler methods
> to make it easier to detect where parameter entities are used
> within a content model. However, the internalEntityDecl
> method on the XMLDTDHandler interface only provides you the
> normalized value of the entity. Therefore, I think we need
> to add another parameter to this method to pass the non-
> normalized value. For example:
>
> public void internalEntityDecl(String name, XMLString value,
> XMLString nonNormalizedValue)
> throws XNIException;
This is, of course, needed if we remove the entity related methods from
XMLAttributes interface.
Pavani
--
Pavani Mukthipudi
Sun Microsystems Inc.
Phone: 080 - 2298989 Extn: 87390
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
