Re: Locator2 is wrong

----- Original Message ----- 
From: "Elliotte Rusty Harold" <[email protected]>
To: "Karl Waclawek" <[email protected]>
Cc: <[email protected]>
Sent: Sunday, April 25, 2004 1:13 PM

> At 12:07 PM -0400 4/25/04, Karl Waclawek wrote:
> 
> >The Locator interface provides entity related information, i.e. the
> >external Id (systemId, publicId). Even the line and column numbers
> >are specific to the 'current' entity. It makes sense to tie in other entity
> >related information, like XML version and encoding.
> 
> That makes a little more sense, but still the interface is called 
> Locator, not EntityInfo. The system ID, public ID, line and column 
> number, are necessary to find the current location of the event. The 
> encoding and version are not.

Well, the encoding might be useful as well for that purpose,
if you really want to access the line and column.

> Perhaps we could just rename Locator2 
> EntityInfo? I could believe that an EnitytInfo is a Locator; but no. 
> Line and column numbers are not part of the entity info.  They are 
> different things. Hmm...

You could call it EntityParseInfo, as the info is related to
the entity in the context of parsing. I agree, Locator
is not the best name - but what about backwards compatibility?

Considering this, there might be some runtime features/properties
that could be members of such an interface rather than
features or properties. Example: is-standalone.

Karl


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
List: sax-devel, [email protected]
See:  http://www.saxproject.org/
https://lists.sourceforge.net/lists/listinfo/sax-devel