Home / Browse / SAX: Simple API for XML / Mail / Archive

SAX: Simple API for XML

Email Archive: sax-devel (read-only)

2001:	_Jan	_Feb	_Mar	_Apr	_May	_Jun	_Jul (6)	_Aug (52)	_Sep (3)	_Oct (29)	_Nov (97)	_Dec (5)
2002:	_Jan (55)	_Feb (33)	_Mar (3)	_Apr (32)	_May (92)	_Jun (51)	_Jul (3)	_Aug (4)	_Sep (6)	_Oct (6)	_Nov (3)	_Dec (6)
2003:	_Jan (5)	_Feb (2)	_Mar (1)	_Apr (16)	_May	_Jun (14)	_Jul (3)	_Aug (2)	_Sep	_Oct (3)	_Nov (12)	_Dec (3)
2004:	_Jan (4)	_Feb (34)	_Mar (54)	_Apr (143)	_May	_Jun (7)	_Jul (2)	_Aug	_Sep (1)	_Oct	_Nov (4)	_Dec (6)
2005:	_Jan (11)	_Feb	_Mar	_Apr (1)	_May	_Jun	_Jul	_Aug	_Sep	_Oct	_Nov	_Dec
2006:	_Jan (2)	_Feb (6)	_Mar (2)	_Apr	_May (10)	_Jun	_Jul	_Aug	_Sep	_Oct	_Nov (2)	_Dec (1)
2007:	_Jan	_Feb	_Mar (1)	_Apr	_May	_Jun (1)	_Jul	_Aug	_Sep	_Oct	_Nov (2)	_Dec
2008:	_Jan	_Feb	_Mar	_Apr (4)	_May	_Jun	_Jul	_Aug	_Sep	_Oct	_Nov	_Dec
2010:	_Jan	_Feb	_Mar	_Apr	_May	_Jun	_Jul	_Aug (1)	_Sep	_Oct	_Nov	_Dec
2011:	_Jan	_Feb	_Mar (1)	_Apr	_May	_Jun	_Jul	_Aug	_Sep	_Oct	_Nov	_Dec


S	M	T	W	T	F	S
	1	2	3	4	5	6

7	8	9	10	11	12	13
				(3)
14	15	16	17	18	19	20
					(1)
21	22	23	24	25	26	27

28	29	30

[Sax-devel] JavaDoc Thinko

From: Elliotte Harold <elharo@me...> - 2004-11-19 21:22

The JavaDoc for InputSource states, "If neither a character stream nor a 
byte stream is available, the parser will attempt to open a URI 
connection to the resource identified by the system identifier."

I suspect at some point someone did a find and replace for URL/URI in 
the Javadoc. However. there's no such thing as a "URI connection". This 
should read "URLConnection" or perhaps "URL connection", but it 
definitely is a URL connection, not a URI connection.

David, could you fix this in CVS please? Thanks.


-- 
Elliotte Rusty Harold  elharo@...
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim

[Sax-devel] SAX for .NET 1.0

From: Karl Waclawek <karl@wa...> - 2004-11-11 14:46

A belated announcement (I thought this list was more or less dead):

The SAX API has been ported to the .NET environment.
Check out http://saxdotnet.sourceforge.net
A non-validating parser implementation, based on Expat,
has been provided as well (package SAXExpat 1.0).

Karl

[Sax-devel] Locator position

From: Petr Cimprich <petr@gi...> - 2004-11-11 10:08

Hi all,

I would like to ask what have been reasons to recommend that SAX drivers 
should provide the line and column position of the first character 
_after_ the text associated with the current document event 
(http://www.saxproject.org/apidoc/org/xml/sax/Locator.html). It appears 
more natural to provide a position within text associated with the 
current event, for the first sight. Am I missing some relevant benefits 
of the way SAX uses to specify the position?

Thanks,
Petr

-- 
Petr Cimprich
Ginger Alliance
 http://www.gingerall.com

Re: [Sax-devel] Locator position

From: Petr Cimprich <petr@gi...> - 2004-11-11 14:17

David Megginson wrote:

>
>Originally, SAX was designed to work with existing XML parsers -- it
>was only later that things turned around and people started designing
>parsers to work with SAX.  Reporting a position right after the markup
>worked best with the existing XML parsers.
>
>Actually, I'm not sure I see the advantage of reporting a position
>before or inside.  Ideally, you'd have the whole range (start-end),
>but if you cannot have that, one position is just as good as another
>for reporting errors to the user.
>  
>

I have thought this is quite arbitrary, just hasn't been sure. The 
reason why I ask is that we are specifying the locator behavior for Perl 
SAX and we want neither introduce unnecessary differences from Java nor 
follow the Java API blindly.

Thanks,
Petr

-- 
Petr Cimprich
Ginger Alliance
 http://www.gingerall.com