Re: RFC: Schema annotation support

On Wed, 2 Apr 2003, Khaled Noaman wrote: > There has been a demand for annotation support which is ignored > after validation. I have few comments regarding your proposed > solution. You are storing references to the appinfo/documentation > dom nodes. First, this means that you are keeping around

Re: RFC: Schema annotation support

On Wed, 2 Apr 2003, Neil Graham wrote: > Hi all, > > Just as another datapoint, there exists an (as yet unimplemented) interface > for accessing the contents of xs:annotations in Xerces-J. Go to > http://xml.apache.org/xerces2-j/javadocs/xerces2/index.html and look at the > XSAnnotation class fo

Re: RFC: Schema annotation support

Can we change the default behaviour of ln in gmake install to that of cp... using ln -sf ? ;) cp -fp /home/all/XML/xml-xerces/c/lib/libxerces-c.so.23.0 /usr/local/lib (cd /usr/local/lib; ln -s libxerces-c.so.23.0 libxerces-c.so.23; ln -s libxerces-c.so.23.0 libxerces-c.so) ln: `libxerces-c.so':

xerces shared lib size

hi, We are trying to use part of the xerce lib functions in a resource constrained embedded PC. We have encountered a problem that we don't really have enough space to put the whole xerce library on the embedded PC. I tried to use -static flag in gcc in order to link to xerce lib statically (i

Re: Datatype question

Image people write a binary number in a check. Obviously base 10 is a more natural way. The same goes to schema/instance document author. Rgds, PeiYong - Original Message - From: "Bagepalli, Kiran" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 02, 2003 2:16 PM Subject

RE: Datatype question

The short answer: the exponent in the text representations of floats (and doubles) is base 10. The long answer: m × 2^e explicitly refers to the value space of floats (that is, the range of values that can be represented), not the lexical (text) representation that shows up in a document. The pow

Datatype question

Is the exponent in a float or double type, base 2 or it is base 10. 2^X or 10^X. The schema spec says "100" and "1.0E2" are the same . At the same time it also says the float consists of the values m × 2^e Can someone clarify which definition is correct. Thanks Kiran   --

RE: RFC: Schema annotation support

On Wed, 2 Apr 2003, Bagepalli, Kiran wrote: > A small glitch when I started using the code. > > If I have XML embedded in the documentation > for eg. > > 12S1 > > > Ideally speaking if I get the documentation I would be expecting a text of > 12S1. > However the traverseSchema DOM eats aw

RE: RFC: Schema annotation support

A small glitch when I started using the code. If I have XML embedded in the documentation for eg. 12S1 Ideally speaking if I get the documentation I would be expecting a text of 12S1. However the traverseSchema DOM eats away this as a Node and only return 12S1. This forces me escape all t

Any way to check for open child nodes before using release?

I was wondering if there is any way to check whether any references to child nodes, etc, are open before calling release? Basically, I allow users to "close" any reference they choose. As currently implemented, my code will just call release on the node and therefore close any nodes below it. I

Re: Implementing getTextContent

Hi, all, I gonna check in Erik's code (thanks Erik), and draft an FAQ on the method(s) to clarify the ownership issue of the returned text. Rgds, PeiYong - Original Message - From: "Erik Rydgren" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 02, 2003 4:40 AM Sub

Re: SAXPrint not printing DOCTYPE

As Neil mentioned in a previous note, you need to check SAX2 and not SAX. Take a look at SAX2XMLReaderImpl::doctypeDecl. Khaled Adam Rogoyski wrote: > On Wed, 2 Apr 2003, Gareth Reakes wrote: > > > Hi, > > DOMPrint uses DOMWriter while the SAX programs print stuff out > > based on SAX even

Re: SAXPrint not printing DOCTYPE

On Wed, 2 Apr 2003, Gareth Reakes wrote: > Hi, > DOMPrint uses DOMWriter while the SAX programs print stuff out > based on SAX events. To implement it in the SAX programs you would need to > write the appropriate handler in the SAXPrintHandler file. I believe that > doctypeDecl will do what

Re: RFC: Schema annotation support

Sure, here it is: class VALIDATORS_EXPORT SchemaAnnotation { public : // --- // Constructors and Destructors // --- SchemaAnnotation(); ~

Re: SAXPrint not printing DOCTYPE

Hi, I believe sax2/DeclHandler is (at least) what you'll need. Cheers! Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] |-+> | | Gareth Reakes| | |

Re: RFC: Schema annotation support

Hi all, Just as another datapoint, there exists an (as yet unimplemented) interface for accessing the contents of xs:annotations in Xerces-J. Go to http://xml.apache.org/xerces2-j/javadocs/xerces2/index.html and look at the XSAnnotation class for details. Implementation would be tricky I'll admi

Re: DOMWriter->writeNode with DocumentFragment

Elliot, You may do the verification once the fix is in the nightly build. Rgds, PeiYong - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 01, 2003 6:06 PM Subject: DOMWriter->writeNode with DocumentFragment > When I try to "get XML" on a DO

Re: SAXPrint not printing DOCTYPE

Hi, DOMPrint uses DOMWriter while the SAX programs print stuff out based on SAX events. To implement it in the SAX programs you would need to write the appropriate handler in the SAXPrintHandler file. I believe that doctypeDecl will do what you need although its been a while since I used

Re: RFC: Schema annotation support

> There has been a demand for annotation support which is ignored > after validation. I have few comments regarding your proposed > solution. You are storing references to the appinfo/documentation > dom nodes. First, this means that you are keeping around the whole > dom tree in memory. Second,

Re: RFC: Schema annotation support

There has been a demand for annotation support which is ignored after validation. I have few comments regarding your proposed solution. You are storing references to the appinfo/documentation dom nodes. First, this means that you are keeping around the whole dom tree in memory. Second, once the sch

SAXPrint not printing DOCTYPE

Hi. The SAXPrint and SAX2Print sample code do not print out the

Re: RFC: Schema annotation support

On Wed, 2 Apr 2003, Gareth Reakes wrote: > Hi, > we saw it :) We were just waiting for the most appropriate person > to answer. I guess that has come down to me. There was some code written a > while ago that did this. I did not make it into the last version. There is > some demand for it

DO NOT REPLY [Bug 18611] New: - Scanner permits some invalid character references.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: RFC: Schema annotation support

Hi, we saw it :) We were just waiting for the most appropriate person to answer. I guess that has come down to me. There was some code written a while ago that did this. I did not make it into the last version. There is some demand for it and I would be happy to review/ commit the code i

RFC: Schema annotation support

Did this message get eaten somewhere? Nobody responded to me. =snif= I may not be the best of programmers, but I'd still like to help. :) Should this be an issue for the list? Post to bugzilla? Just send the patch? (I'd like to clean it up first, though... after some good suggestions) -Ric

RE: LAX Validation

At 15.35 01/04/2003 -0800, you wrote: Actually I do not understand how multiple schema locations can be specified and also multiple nonamespace locations. Is setExternalSchemaLocation a URI or a flag? I could have a document validating against a.dtd, b.xsd, c.xsd(namespace X), d.xsd(namespace Y). I

RE: Implementing getTextContent

No keep the DOM API as it is. The DOMNode function has not changed. But now the new function is available in DOMNodeImpl for those with special memory management needs. / Erik -Original Message- From: Gareth Reakes [mailto:[EMAIL PROTECTED] Sent: den 2 april 2003 11:14 To: [EMAIL PROTECT

RE: Implementing getTextContent

Hi, are you suggesting we should extend the DOM with a proprietary method? In this case I'm not completely against it considering that the DOM specs pay no attention to memory management. Another alternative would be to put the method in the impl file and cast down to it. Gareth On W

RE: Implementing getTextContent

I agree that this is a good way of providing both functionalities and it actually made implementation a bit easier. I took the liberty to write the whole shabang down in code. This is written direcly from the specifications now. As always the code compiles but it is untested. Please verify. Regard