From xerces-j-debbie17@example.org Mon Jun 03 09:25:35 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 95922 invoked by uid 500); 3 Jun 2002 09:25:34 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 95912 invoked from network); 3 Jun 2002 09:25:34 -0000 Message-ID: <debbie17@example.org> Date: Mon, 03 Jun 2002 11:25:15 +0200 From: debbie17@example.org (Dennis Thrysoe - Netnord A/S) Organization: Netnord A/S User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523 X-Accept-Language: en-us, en MIME-Version: 1.0 To: debbie17@example.org Subject: Validating without parsing Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, I was wondering if the XNI component approach to building a parser would make it easy to use the XMLSchemaValidator or XMLDTDValidator to validate generated XML fragments, without parsing a document. Oh, and by the way. Is anything included in Xerces 2 that can serialize SAX events into a document? TIA, -dennis --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Mon Jun 03 12:24:50 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 68479 invoked by uid 500); 3 Jun 2002 12:24:49 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 68470 invoked from network); 3 Jun 2002 12:24:49 -0000 Message-ID: <debbie17@example.org> Date: Mon, 03 Jun 2002 21:25:06 +0900 From: Andy Clark <debbie17@example.org> X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: debbie17@example.org Subject: Re: Validating without parsing References: <debbie17@example.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 03 Jun 2002 12:42:01.0605 (UTC) FILETIME=[0ECB8350:01C20AFC] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Dennis Thrysoe - Netnord A/S wrote: > I was wondering if the XNI component approach to building a parser would > make it easy to use the XMLSchemaValidator or XMLDTDValidator to > validate generated XML fragments, without parsing a document. Sure, that's possible but there's currently no code to make this doable directly. > Oh, and by the way. Is anything included in Xerces 2 that can serialize > SAX events into a document? Check out the org.apache.xml.serialize package. You could also use a SAXSource as an input to Xalan (via TrAX) and the identity transform (i.e. no stylesheet) to do the same thing. -- Andy Clark * debbie17@example.org --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Mon Jun 03 12:48:45 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 86906 invoked by uid 500); 3 Jun 2002 12:48:44 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 86897 invoked from network); 3 Jun 2002 12:48:44 -0000 Message-ID: <debbie17@example.org> Date: Mon, 03 Jun 2002 14:48:10 +0200 From: debbie17@example.org (Dennis Thrysoe - Netnord A/S) Organization: Netnord A/S User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523 X-Accept-Language: en-us, en MIME-Version: 1.0 To: debbie17@example.org Subject: Re: Validating without parsing References: <debbie17@example.org> <debbie17@example.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Andy Clark wrote: > Dennis Thrysoe - Netnord A/S wrote: > >>I was wondering if the XNI component approach to building a parser would >>make it easy to use the XMLSchemaValidator or XMLDTDValidator to >>validate generated XML fragments, without parsing a document. > > > Sure, that's possible but there's currently no code to > make this doable directly. Great. What would then be the best way to specify a filename, Reader or similar with the schema data in it? -dennis --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Mon Jun 03 13:16:25 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 4722 invoked by uid 500); 3 Jun 2002 13:16:24 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 4702 invoked from network); 3 Jun 2002 13:16:23 -0000 Subject: [PSVI] full support is available To: debbie17@example.org, debbie17@example.org X-Mailer: Lotus Notes Release 5.0.4a July 24, 2000 Message-ID: <debbie17@example.org> From: debbie17@example.org Date: Mon, 3 Jun 2002 09:16:11 -0400 X-MIMETrack: Serialize by Router on D25ML04/25/M/IBM(Release 5.0.8 |June 18, 2001) at 06/03/2002 09:16:22 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi all, Now the full PSVI information can be retrieved from XNI augmentation. >From within an XMLDocumentHandler (DOM/SAX parsers, for example), one can 1. Get an ElementPSVI from the XNI augmentation of the validation root (normally the root element); 2. Get XSModel from it by calling ElementPSVI#getSchemaInformation(); 3. Get a list of XSNamespaceItem by XSModel#getNamespaceItems(); 4. From each XSNamespaceItem, get its target namespace, components of that namespace, and document locations that contribute to that namespace. There are things that need to be revisited: 1. Method names: getIsXXX. 2. How to represent annotations. 3. How to represent a document information item (the [document] PSVI property "http://www.w3.org/TR/xmlschema-1/#sd-document"). Future plans: - Convert preloaded grammars to XSModel, so that users can examine schema components in preloaded grammars; - Provide PSVI via DOM (possibly controlled by a feature) Cheers, Sandy Gao Software Developer, IBM Canada 8005871587 debbie17@example.org --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Mon Jun 03 18:46:55 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 63477 invoked by uid 500); 3 Jun 2002 18:46:55 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 63468 invoked from network); 3 Jun 2002 18:46:54 -0000 Message-ID: <F0C169880391D311A5D10000D1ECDC2E0878786D@EXCHANGE> From: "Domingo, John" <debbie17@example.org> To: debbie17@example.org Subject: Question regarding Xerces2 and the org.apache.xerces.readers clas ses Date: Mon, 3 Jun 2002 11:46:58 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N All, I just began a migration of Java apps from the Xerces1 libraries to the Xerces2 libraries. One thing that I ran into is that the packages org.apache.xerces.readers and org.apache.xerces.domx do not exist in the Xerces2 xercesImpl.jar file, and my current code (which is using Xerces v1.4.3) has dependencies on some the classes under these packages (e.g., MIME2Java, XGrammarWriter). Can anyone provide me any direction on where I can find them now? Or if they are all deprecated, can anyone provide any suggestions on how I should proceed? Thanks in advance! ___________________________ "FUTILITY in Golf - You'll always miss 100% of the shots you don't take, and, statistically speaking, 99% of the shots you do." - Anonymous John P. Domingo Senior Software Engineer Software Integration Group (SIG) GERS, Inc. Wateridge Technology Center 10431 Wateridge Circle San Diego, CA 92121 8005871587, direct 8005871587 --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Tue Jun 04 05:31:38 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 63887 invoked by uid 500); 4 Jun 2002 05:31:38 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 63875 invoked from network); 4 Jun 2002 05:31:37 -0000 Message-ID: <debbie17@example.org> Date: Tue, 04 Jun 2002 14:31:58 +0900 From: Andy Clark <debbie17@example.org> X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: debbie17@example.org Subject: Re: Question regarding Xerces2 and the org.apache.xerces.readers classes References: <F0C169880391D311A5D10000D1ECDC2E0878786D@EXCHANGE> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Jun 2002 05:49:01.0580 (UTC) FILETIME=[872984C0:01C20B8B] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N "Domingo, John" wrote: > Can anyone provide me any direction on where I can find them now? > Or if they are all deprecated, can anyone provide any suggestions on how I > should proceed? xerces.readers.MIME2Java -> xerces.util.EncodingMap As for the XGrammarWriter, I don't think we have an equivalent in Xerces2 at the moment. But... I'm currently writing a tool to simplify some batch XSLT transformations. And just the other day I wrote a processor that uses the Xerces2 DTD scanner to read a DTD and produce an XML representation of it. From that, I imagine that it would be very simple to write an XSLT stylesheet to write it back to DTD syntax or even XML Schema syntax. And since Xerces2 reports a lot of the parameter entity boundaries, perhaps some minor processing could be done to identify commonly used parameter entities within content models, etc. and generate appropriate model groups and type hierarchies in the resultant XML Schema. I hope to get some time within the next few days to wrap up the code that I have now and add it to my list of freely available projects on my web page. Perhaps this code will help you find a solution to your problem. -- Andy Clark * debbie17@example.org --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Tue Jun 04 19:10:39 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 79652 invoked by uid 500); 4 Jun 2002 19:10:38 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 79633 invoked from network); 4 Jun 2002 19:10:37 -0000 Message-ID: <debbie17@example.org> Date: Tue, 04 Jun 2002 15:10:06 -0400 From: Elena Litani <debbie17@example.org> X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: debbie17@example.org, debbie17@example.org Subject: DOM tree (re)validation is implemented! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N The latest Xerces code supports revalidation of a DOM tree against XML Schema grammars. The code could be downloaded at: http://gump.covalent.net/jars/latest/xml-xerces2/ The support is available via DOM L3 implementation of normalizeDocument() [1]. Comments/feedback/bug-reports are VERY welcome. :) IMPORTANT!! ----------- The code is experimental: the methods/classes could be removed, modified, or renamed. In particular, in the latest code the DOM L3 functionality is accessible via org.apache.xerces.dom.DocumentImpl. However, we want to try to reorganize Xerces DOM implementation code to separate DOM L2 from DOM L3 implementations. Thus, in the future DOM L3 functionality could be moved to another class. Parsing documents ----------------- Use DOMBuilder parser instead of DOMParser if you plan to revalidate a document. You can create the DOMBuilder as follows: (a) new org.apache.xerces.parser.DOMBuilderImpl(); (b) call org.apache.xerces.dom.DOMImplementationImpl.createDOMBuilder() How to tell DOM implementation to revalidate the tree ------------------------------------------------------ DOM L3 provides setNormalizationFeature()[2] on the Document interface that allows users to specify what functions normalizeDocument() should perform. (1) Cast Document to DocumentImpl. (2) Call document.setNormalizationFeature("validate", true). (3) To start (re)validation call document.normalizeDocument(). How to specify grammar for a document ------------------------------------- (1) The documentElement must have xsi:schemaLocation or xsi:noSchemaLocation attributes that specify schema location(s). (2) The documentURI [3] must be set. The location of the schema documents will be resolved relative to documentURI. How to register error handler ------------------------------ Use DOM L3 setErrorHandler() [4] method to attach error handler to the Document. You need to cast to DocumentImpl to be able to call this method. Limitations ----------- - Revalidation of the DOM tree against DTD grammar is not supported. - EntityRefence, CDATASection content will not be validated. - Schema normalized values won't be exposed via the tree after DOM revalidation. The element default value (the one that is added by XML Schema validator) won't be exposed via DOM tree. - Attribute value normalization - the code does not normalize attribute values per XML 1.0 (type CDATA). That means that XML Schema validator may not be normalizing attribute values correctly. Thanks, [1] http://www.w3.org/TR/2002/WD-DOM-Level-3-Core-20020409/core.html#Document3-normalizeDocument [2] http://www.w3.org/TR/2002/WD-DOM-Level-3-Core-20020409/core.html#Document3-setNormalizationFeature [3] http://www.w3.org/TR/2002/WD-DOM-Level-3-Core-20020409/core.html#Document3-documentURI -- Elena Litani / IBM Toronto --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Tue Jun 04 19:16:01 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 84481 invoked by uid 500); 4 Jun 2002 19:16:01 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 84471 invoked from network); 4 Jun 2002 19:16:00 -0000 Message-ID: <debbie17@example.org> Date: Tue, 04 Jun 2002 15:15:24 -0400 From: Elena Litani <debbie17@example.org> X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: debbie17@example.org Subject: Re: Validating without parsing References: <debbie17@example.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Dennis hi, Dennis Thrysoe - Netnord A/S wrote: > I was wondering if the XNI component approach to building a parser would > make it easy to use the XMLSchemaValidator or XMLDTDValidator to > validate generated XML fragments, without parsing a document. Yes, this is the approach we used to implement DOM revalidation in Xerces. I expect more discussion on revalidation design on xerces-j-dev list. If you are interested, please subscribe to this list. Thank you, -- Elena Litani / IBM Toronto --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Tue Jun 04 19:17:15 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 87247 invoked by uid 500); 4 Jun 2002 19:17:15 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 87236 invoked from network); 4 Jun 2002 19:17:14 -0000 Message-ID: <debbie17@example.org> Date: Tue, 04 Jun 2002 15:16:53 -0400 From: Elena Litani <debbie17@example.org> X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: debbie17@example.org Subject: Re: Support for XPath in Xerces2 References: <000001c2082d$609c9420$030a0a0a@dad> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi Lynn, Lynn Monson wrote: > Could anyone summarize the status of XPath support in Xerces2? There is no support and there are no plans to support XPath in Xerces2. You should check with Xalan team if they plan to implement it. Thx, -- Elena Litani / IBM Toronto --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Tue Jun 04 19:24:41 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 94024 invoked by uid 500); 4 Jun 2002 19:24:37 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 94010 invoked from network); 4 Jun 2002 19:24:36 -0000 Message-ID: <debbie17@example.org> Date: Tue, 04 Jun 2002 15:24:24 -0400 From: Elena Litani <debbie17@example.org> X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: debbie17@example.org Subject: Re: question about DOM/DOM2 behavior wrt namespaces References: <debbie17@example.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi Paul, Paul Brown wrote: > However... With namespace awareness turned on, calling getAttributes() returns a NodeList of DOM1 attributes With W3C DOM, calling getAttributes() returns NamedNodeMap, that represents collection of attributes. To retrieve attributes after namespace aware processing, use getNamedItemNS() method instead of getNamedItem(). If you are interested in the test suites for W3C DOM, take a look at the test suite developed by the W3C: http://www.w3.org/DOM/Test/ Hope it helps, -- Elena Litani / IBM Toronto --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Tue Jun 04 20:02:48 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 17596 invoked by uid 500); 4 Jun 2002 20:02:48 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 17587 invoked from network); 4 Jun 2002 20:02:47 -0000 From: "Lynn Monson" <debbie17@example.org> To: <debbie17@example.org> Subject: RE: Support for XPath in Xerces2 Date: Tue, 4 Jun 2002 14:02:38 -0600 Message-ID: <000301c20c02$ca4802a0$030a0a0a@dad> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: <debbie17@example.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N OK, thanks Elena. I was just wondering if Xerces would need/want a donated XPath implementation as a basis for DOM Level 3 XPath support. > -----Original Message----- > From: Elena Litani [mailto:debbie17@example.org] > Sent: Tuesday, June 04, 2002 1:17 PM > To: debbie17@example.org > Subject: Re: Support for XPath in Xerces2 > > > Hi Lynn, > > Lynn Monson wrote: > > Could anyone summarize the status of XPath support in Xerces2? > > There is no support and there are no plans to support XPath > in Xerces2. > > You should check with Xalan team if they plan to implement it. > > Thx, > -- > Elena Litani / IBM Toronto > > --------------------------------------------------------------------- > To unsubscribe, e-mail: debbie17@example.org > For additional commands, e-mail: debbie17@example.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Tue Jun 04 21:32:39 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 94872 invoked by uid 500); 4 Jun 2002 21:32:38 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 94852 invoked from network); 4 Jun 2002 21:32:37 -0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: question about DOM/DOM2 behavior wrt namespaces Date: Tue, 4 Jun 2002 17:32:39 -0400 Message-ID: <debbie17@example.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: question about DOM/DOM2 behavior wrt namespaces Thread-Index: AcIL/YN2Rdl3dnqvRMa4MMPipZ2VqgAA+V4Q From: "Paul Brown" <debbie17@example.org> To: <debbie17@example.org> Cc: "Elena Litani" <debbie17@example.org> X-OriginalArrivalTime: 04 Jun 2002 21:32:39.0849 (UTC) FILETIME=[5A47C190:01C20C0F] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, Elena -- > > [Paul Brown] > > However... With namespace awareness turned on, calling=20 > getAttributes() returns a NodeList of DOM1 attributes=20 > [Elena Litani] > With W3C DOM, calling getAttributes() returns NamedNodeMap, that > represents collection of attributes. > To retrieve attributes after namespace aware processing, use > getNamedItemNS() method instead of getNamedItem(). You got me... NamdeNodeMap is what I meant. :) NamedNodeMap does not = inherit from NodeList; they do share the item(int) method. Since I want all attributes in a particular namespace, I can't use the = getNamedItemNS(); I'm attempting to use item(int) to iterate through the = list and get the items. (It would be nice to use XPath, but this is a = test suite for an XPath implementation...) Other DOM implementations = (e.g., GNU JAXP) appear to do the right thing, i.e., return the = attributes with namespace information. -- Paul --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Wed Jun 05 15:12:23 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 90816 invoked by uid 500); 5 Jun 2002 15:12:23 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 90805 invoked from network); 5 Jun 2002 15:12:22 -0000 Message-ID: <debbie17@example.org> From: "GUPTA,SUMIT (HP-NewJersey,ex2)" <debbie17@example.org> To: "'debbie17@example.org'" <debbie17@example.org> Subject: settings for validation against both a schema and a DTD Date: Wed, 5 Jun 2002 11:12:20 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, I am trying to dynamically validate an xml document against either a referenced schema or a dtd, I have set the following features on a DocumentBuilderFactory, factory.setAttribute( "http://apache.org/xml/features/allow-java-encodings", true ); factory.setAttribute( "http://apache.org/xml/features/validation/schema", true ); factory.setAttribute( "http://apache.org/xml/features/validation/dynamic", true ); Using the DocumentBuilder to parse works fine for documents with schema references, but logs warnings like the one below for documents referencing a DTD. schema_reference.4: Failed to read schema document 'null', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. Is there a setting that will enable me to dynamically validate a document against either a DTD or a schema? Thanks in advance. sumit --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Wed Jun 05 22:16:29 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 71748 invoked by uid 500); 5 Jun 2002 22:16:29 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 71733 invoked from network); 5 Jun 2002 22:16:28 -0000 Message-ID: <debbie17@example.org> Date: Wed, 05 Jun 2002 15:16:35 -0700 From: Mark Woon <debbie17@example.org> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0+) Gecko/20020525 X-Accept-Language: en-us, en MIME-Version: 1.0 To: debbie17@example.org Subject: Modifying schema validation Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hello... I've just started playing with Xerces, and I'm trying to figure out how to hook into the schema validator. In particular, I'm interested in adding new constraints for my own work so that I can define dependencies (eg. element a is required if element b is not specified, element a is only required if attribute x is not present, etc.) in my schema. Can anyone point me in the right direction? Thanks, -Mark --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Thu Jun 06 06:16:52 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 86994 invoked by uid 500); 6 Jun 2002 06:16:51 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 86984 invoked from network); 6 Jun 2002 06:16:51 -0000 Message-ID: <debbie17@example.org> Date: Thu, 06 Jun 2002 08:16:59 +0200 From: debbie17@example.org (Dennis Thrysoe - Netnord A/S) Organization: Netnord A/S User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523 X-Accept-Language: en-us, en MIME-Version: 1.0 To: debbie17@example.org Subject: Re: Validating without parsing References: <debbie17@example.org> <debbie17@example.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Elena Litani wrote: > Dennis hi, > > Dennis Thrysoe - Netnord A/S wrote: > >>I was wondering if the XNI component approach to building a parser would >>make it easy to use the XMLSchemaValidator or XMLDTDValidator to >>validate generated XML fragments, without parsing a document. > > Yes, this is the approach we used to implement DOM revalidation in > Xerces. Great. That looks like, I can do something simlar then. > I expect more discussion on revalidation design on xerces-j-dev list. > If you are interested, please subscribe to this list. Actually I'm only searching for the best way to instantiate an XMLSchemaValidator or XMLDTDValidator, specify some named resource to load the grammar from, and the rest *should* be a breeze... Does anybody have any good suggestions or pointers for relevant documentation? -dennis --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Thu Jun 06 08:37:32 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 65651 invoked by uid 500); 6 Jun 2002 08:37:31 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 65639 invoked from network); 6 Jun 2002 08:37:30 -0000 From: "Marcial Atienzar" <debbie17@example.org> To: <debbie17@example.org> Subject: How can I parse HTML not XTML? Date: Thu, 6 Jun 2002 10:41:34 +0200 Message-ID: <debbie17@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <debbie17@example.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hello, I've this code: DOMParser parser = new DOMParser(); HTMLDocument document = null; try { parser.setProperty("http://apache.org/xml/properties/dom/document-class-name ", "org.apache.html.dom.HTMLDocumentImpl"); parser.parse(archivo); document = (HTMLDocument)parser.getDocument(); ... And with this code I can't parse HTML, only XHTML. I've an error when I try to do it. A lot of thanks, Marcial Atienzar Navarro --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Thu Jun 06 08:54:54 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 80670 invoked by uid 500); 6 Jun 2002 08:54:54 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 80656 invoked from network); 6 Jun 2002 08:54:52 -0000 Message-ID: <debbie17@example.org> Date: Thu, 6 Jun 2002 04:55:53 -0400 From: SB <debbie17@example.org> To: debbie17@example.org Subject: Re: How can I parse HTML not XTML? References: <debbie17@example.org> <debbie17@example.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1 In-Reply-To: <debbie17@example.org>; from Marcial Atienzar on Thu, Jun 06, 2002 at 10:41:34AM +0200 X-Mailer-Info: http://www.mutt.org/ X-Editor: Vi-forever X-Whoami: 'Rum pel stil skin' X-Comment: 'mutt is mutty' X-Questoin: 'Is there a limit to the number of headers' X-Uptime: 4:51am up 51 days, 14:18, 51 users, load average: 4.98, 4.65, 4.88 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Quoting Marcial Atienzar (debbie17@example.org): > > And with this code I can't parse HTML, only XHTML. I've an error when I try > to do it. A lot of thanks, > You will have to XMLize your HTML before using the DOMParser - tools for these are NekoHTML and JTidy. http://www.apache.org/~andyc/nekohtml/doc/index.html http://sourceforge.net/projects/jtidy --st. --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Thu Jun 06 09:31:28 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 12062 invoked by uid 500); 6 Jun 2002 09:31:27 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 12047 invoked from network); 6 Jun 2002 09:31:27 -0000 From: "Marcial Atienzar" <debbie17@example.org> To: <debbie17@example.org> Subject: RE: How can I parse HTML not XTML? Date: Thu, 6 Jun 2002 11:35:31 +0200 Message-ID: <debbie17@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <debbie17@example.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Thanks, I'm going to try it. -----Mensaje original----- De: SB [mailto:debbie17@example.org] Enviado el: jueves, 06 de junio de 2002 10:56 Para: debbie17@example.org Asunto: Re: How can I parse HTML not XTML? Quoting Marcial Atienzar (debbie17@example.org): > > And with this code I can't parse HTML, only XHTML. I've an error when I try > to do it. A lot of thanks, > You will have to XMLize your HTML before using the DOMParser - tools for these are NekoHTML and JTidy. http://www.apache.org/~andyc/nekohtml/doc/index.html http://sourceforge.net/projects/jtidy --st. --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Thu Jun 06 14:57:17 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 60837 invoked by uid 500); 6 Jun 2002 14:57:17 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 60827 invoked from network); 6 Jun 2002 14:57:16 -0000 thread-index: AcINag7rypsc3Ch6RrSLJE32+zxQpw== Thread-Topic: How can I parse HTML not XTML? From: "otisg" <debbie17@example.org> To: <debbie17@example.org> Cc: Bcc: Subject: Re: How can I parse HTML not XTML? Date: Thu, 6 Jun 2002 07:54:28 -0700 Message-ID: <debbie17@example.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_005C_01C20D2F.628F55E0" X-Mailer: Microsoft CDO for Exchange 2000 Content-Class: urn:content-classes:message Importance: normal Priority: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------=_NextPart_000_005C_01C20D2F.628F55E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Try using NekoHTML. I've tried JTidy and it works, but it's development is almost non-existant from what I can tell, and it supports only DOM. NekoHTML allows you to use DOM, SAX, XNI and its author is actively developing it. Otis _______________________________________________________________ Sign up for FREE iVillage newsletters <http://s.ivillage.com/rd/16705> . >From health and pregnancy to shopping and relationships, iVillage has the scoop on what matters most to you. <-----Original Message-----> > > From: Marcial Atienzar > Sent: 6/6/2002 1:44:34 PM > To: debbie17@example.org > Subject: How can I parse HTML not XTML? > > Hello, > > I've this code: > > DOMParser parser = new DOMParser(); > HTMLDocument document = null; > try { > > parser.setProperty("http://apache.org/xml/properties/dom/document-class- name > ", > "org.apache.html.dom.HTMLDocumentImpl"); > parser.parse(archivo); > document = (HTMLDocument)parser.getDocument(); > ... > > And with this code I can't parse HTML, only XHTML. I've an error when I try > to do it. A lot of thanks, > > Marcial Atienzar Navarro > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: debbie17@example.org > For additional commands, e-mail: debbie17@example.org > > ------=_NextPart_000_005C_01C20D2F.628F55E0 Content-Type: text/html Content-Transfer-Encoding: 7bit <HTML> <HEAD> <STYLE></STYLE> </HEAD> <BODY> Try using NekoHTML.<br> I've tried JTidy and it works, but it's development is almost non-existant from what I can tell, and it supports only DOM. NekoHTML allows you to use DOM, SAX, XNI and its author is actively developing it.<br> <br> Otis<br> <br> </BODY></HTML> <BR><font face="Arial, Helvetica, sans-serif" size="2" style="font-size:13.5px">_______________________________________________________________<BR>Sign up for <A HREF="http://s.ivillage.com/rd/16705">FREE iVillage newsletters</A>.<BR>From health and pregnancy to shopping and relationships, iVillage<BR>has the scoop on what matters most to you. </font><-----Original Message-----><br> > <br> > From: Marcial Atienzar<br> > Sent: 6/6/2002 1:44:34 PM<br> > To: debbie17@example.org<br> > Subject: How can I parse HTML not XTML?<br> > <br> > Hello,<br> > <br> > I've this code:<br> > <br> > DOMParser parser = new DOMParser();<br> > HTMLDocument document = null;<br> > try {<br> > <br> > parser.setProperty("http://apache.org/xml/properties/dom/document-class-name<br> > ",<br> > "org.apache.html.dom.HTMLDocumentImpl");<br> > parser.parse(archivo);<br> > document = (HTMLDocument)parser.getDocument();<br> > ...<br> > <br> > And with this code I can't parse HTML, only XHTML. I've an error when I try<br> > to do it. A lot of thanks,<br> > <br> > Marcial Atienzar Navarro<br> > <br> > <br> > ---------------------------------------------------------------------<br> > To unsubscribe, e-mail: debbie17@example.org<br> > For additional commands, e-mail: debbie17@example.org<br> > <br> > <br> ------=_NextPart_000_005C_01C20D2F.628F55E0-- From xerces-j-debbie17@example.org Thu Jun 06 20:34:21 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 3231 invoked by uid 500); 6 Jun 2002 20:34:21 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 3219 invoked from network); 6 Jun 2002 20:34:20 -0000 Message-Id: <debbie17@example.org> X-Sender: debbie17@example.org X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 06 Jun 2002 16:34:58 -0400 To: debbie17@example.org From: Daniel Shane <debbie17@example.org> Subject: Is it possible to do context sensitive parsing with Xerces? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi all, I would like to do some parsing using Xerces and found that it is quite easy to do the following. Perform action foo when you encounter element bar. However, I would like to go a step farther and do the following: Perform action foo when the next valid element could be bar. Is it possible to interrogate xerces, while it is parsing a document, to know what are the next valid elements that can appear in the document? I could then use the result to check if bar is part of the list and fire foo if this is the case. Is this possible? Thanks in advance! Daniel Shane --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org From xerces-j-debbie17@example.org Fri Jun 07 09:06:05 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 27295 invoked by uid 500); 7 Jun 2002 09:06:05 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 27283 invoked from network); 7 Jun 2002 09:06:04 -0000 Message-ID: <debbie17@example.org> From: "Anderson, John" <debbie17@example.org> To: "'debbie17@example.org'" <debbie17@example.org> Subject: RE: Modifying schema validation Date: Fri, 7 Jun 2002 11:09:16 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C20E03.00182BB0" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C20E03.00182BB0 Content-Type: text/plain; charset="iso-8859-1" Mark, If you're doing a lot of this, it is probably worth looking at schematron, a schema language which supports co-constraints. The syntax is simple and you can embed schematron instructions in your appinfo elements in the schema. This allows you to declare this stuff declaratively. There are a few validators around which support embedded schematron, and hopefully this is somethign which will be plugged into Xerces in the not too distant future. John -----Original Message----- From: Mark Woon [mailto:debbie17@example.org] Sent: 06 June 2002 00:17 To: debbie17@example.org Subject: Modifying schema validation Hello... I've just started playing with Xerces, and I'm trying to figure out how to hook into the schema validator. In particular, I'm interested in adding new constraints for my own work so that I can define dependencies (eg. element a is required if element b is not specified, element a is only required if attribute x is not present, etc.) in my schema. Can anyone point me in the right direction? Thanks, -Mark --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org The information transmitted by this e-mail message is intended solely for the use of the person to whom or entity to which it is addressed. The message may contain information that is privileged and confidential. Disclosure, dissemination, distribution, review, retransmission to, other use of or taking any action in reliance upon this information by anyone other than the intended recipient is prohibited. If you are not the intended recipient, please do not disseminate, distribute or copy this communication, by e-mail or otherwise. Instead, please notify us immediately by return e-mail (including the original message with your reply) and then delete and discard all copies of the message. Although we have taken precautions to minimize the risk of transmitting viruses we nevertheless advise you to carry out your own virus checks on any attachment to this message. We accept no liability for any loss or damage caused by viruses. ------_=_NextPart_001_01C20E03.00182BB0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2654.45"> <TITLE>RE: Modifying schema validation</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2>Mark,</FONT> </P> <P><FONT SIZE=3D2>If you're doing a lot of this, it is probably worth = looking at schematron, a schema language which supports co-constraints. = The syntax is simple and you can embed schematron instructions in your = appinfo elements in the schema. This allows you to declare this stuff = declaratively.</FONT></P> <P><FONT SIZE=3D2>There are a few validators around which support = embedded schematron, and hopefully this is somethign which will be = plugged into Xerces in the not too distant future. </FONT></P> <P><FONT SIZE=3D2>John</FONT> </P> <P><FONT SIZE=3D2>-----Original Message-----</FONT> <BR><FONT SIZE=3D2>From: Mark Woon [<A = HREF=3D"mailto:debbie17@example.org">mailto:debbie17@example.org= DU</A>]</FONT> <BR><FONT SIZE=3D2>Sent: 06 June 2002 00:17</FONT> <BR><FONT SIZE=3D2>To: debbie17@example.org</FONT> <BR><FONT SIZE=3D2>Subject: Modifying schema validation</FONT> </P> <BR> <P><FONT SIZE=3D2>Hello...</FONT> </P> <P><FONT SIZE=3D2>I've just started playing with Xerces, and I'm trying = to figure out how </FONT> <BR><FONT SIZE=3D2>to hook into the schema validator.&nbsp; In = particular, I'm interested in </FONT> <BR><FONT SIZE=3D2>adding new constraints for my own work so that I can = define dependencies </FONT> <BR><FONT SIZE=3D2>(eg. element a is required if element b is not = specified, element a is </FONT> <BR><FONT SIZE=3D2>only required if attribute x is not present, etc.) = in my schema.</FONT> </P> <P><FONT SIZE=3D2>Can anyone point me in the right direction?</FONT> </P> <P><FONT SIZE=3D2>Thanks,</FONT> <BR><FONT SIZE=3D2>-Mark</FONT> </P> <BR> <BR> <P><FONT = SIZE=3D2>---------------------------------------------------------------= ------</FONT> <BR><FONT SIZE=3D2>To unsubscribe, e-mail: = debbie17@example.org</FONT> <BR><FONT SIZE=3D2>For additional commands, e-mail: = debbie17@example.org</FONT> </P> <P><I><FONT SIZE=3D2>The information transmitted by this e-mail message = is intended solely for the use of the person to whom or entity to which = it is addressed. The message may contain information that is privileged = and confidential.&nbsp; Disclosure, dissemination, distribution, = review, retransmission to, other use of or taking any action in = reliance upon this information by anyone other than the intended = recipient is prohibited. If you are not the intended recipient, please = do not disseminate, distribute or copy this communication, by e-mail or = otherwise. Instead, please notify us immediately by return e-mail = (including the original message with your reply) and then delete and = discard all copies of the message.</FONT></I></P> <P><I><FONT SIZE=3D2>Although we have taken precautions to minimize the = risk of transmitting viruses we nevertheless advise you to carry out = your own virus checks on any attachment to this message. We accept no = liability for any loss or damage caused by viruses.</FONT></I></P> </BODY> </HTML> ------_=_NextPart_001_01C20E03.00182BB0-- From xerces-j-debbie17@example.org Fri Jun 07 09:20:32 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 40876 invoked by uid 500); 7 Jun 2002 09:20:32 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 40867 invoked from network); 7 Jun 2002 09:20:32 -0000 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPartTM-000-68ec3ac5-9ab7-4a30-bf52-a60a12f047ad" Subject: RE: Modifying schema validation X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Fri, 7 Jun 2002 14:52:14 +0530 Message-ID: <debbie17@example.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Modifying schema validation Thread-Index: AcIOAuKDugjkaRO3R2+whMkzgxHNCAAAZ7Lw From: "Sridhar Raju Y" <debbie17@example.org> To: <debbie17@example.org> X-OriginalArrivalTime: 07 Jun 2002 09:22:15.0359 (UTC) FILETIME=[D01684F0:01C20E04] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------=_NextPartTM-000-68ec3ac5-9ab7-4a30-bf52-a60a12f047ad Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C20E04.CF7F5D21" ------_=_NextPart_001_01C20E04.CF7F5D21 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Mark, =20 If we use schematron. I think we need seperate parser which can understand the constraints while parsing the instance document. I dont think this standard xerces parser will do it. Please clarify. =20 regards, Sridhar -----Original Message----- From: Anderson, John [mailto:debbie17@example.org]=20 Sent: Friday, June 07, 2002 2:39 PM To: 'debbie17@example.org' Subject: RE: Modifying schema validation =09 =09 Mark,=20 If you're doing a lot of this, it is probably worth looking at schematron, a schema language which supports co-constraints. The syntax is simple and you can embed schematron instructions in your appinfo elements in the schema. This allows you to declare this stuff declaratively. There are a few validators around which support embedded schematron, and hopefully this is somethign which will be plugged into Xerces in the not too distant future.=20 John=20 -----Original Message-----=20 From: Mark Woon [mailto:debbie17@example.org]=20 Sent: 06 June 2002 00:17=20 To: debbie17@example.org=20 Subject: Modifying schema validation=20 Hello...=20 I've just started playing with Xerces, and I'm trying to figure out how=20 to hook into the schema validator. In particular, I'm interested in=20 adding new constraints for my own work so that I can define dependencies=20 (eg. element a is required if element b is not specified, element a is=20 only required if attribute x is not present, etc.) in my schema. Can anyone point me in the right direction?=20 Thanks,=20 -Mark=20 =09 ---------------------------------------------------------------------=20 To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org=20 The information transmitted by this e-mail message is intended solely for the use of the person to whom or entity to which it is addressed. The message may contain information that is privileged and confidential. Disclosure, dissemination, distribution, review, retransmission to, other use of or taking any action in reliance upon this information by anyone other than the intended recipient is prohibited. If you are not the intended recipient, please do not disseminate, distribute or copy this communication, by e-mail or otherwise. Instead, please notify us immediately by return e-mail (including the original message with your reply) and then delete and discard all copies of the message. Although we have taken precautions to minimize the risk of transmitting viruses we nevertheless advise you to carry out your own virus checks on any attachment to this message. We accept no liability for any loss or damage caused by viruses. ------_=_NextPart_001_01C20E04.CF7F5D21 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>Message</TITLE> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD> <BODY> <DIV><SPAN class=3D184032009-07062002><FONT face=3DTahoma = color=3D#0000ff size=3D2>Hi=20 Mark,</FONT></SPAN></DIV> <DIV><SPAN class=3D184032009-07062002><FONT face=3DTahoma = color=3D#0000ff=20 size=3D2></FONT></SPAN>&nbsp;</DIV> <DIV><SPAN class=3D184032009-07062002><FONT face=3DTahoma = color=3D#0000ff=20 size=3D2>&nbsp; If we use schematron. I think we need seperate parser = which can=20 understand the constraints while parsing the instance=20 document.</FONT></SPAN></DIV> <DIV><SPAN class=3D184032009-07062002><FONT face=3DTahoma = color=3D#0000ff=20 size=3D2>I&nbsp;dont think this standard xerces parser will do it. = Please=20 clarify.</FONT></SPAN></DIV> <DIV><SPAN class=3D184032009-07062002><FONT face=3DTahoma = color=3D#0000ff=20 size=3D2></FONT></SPAN>&nbsp;</DIV> <DIV><SPAN class=3D184032009-07062002><FONT face=3DTahoma = color=3D#0000ff=20 size=3D2>regards,</FONT></SPAN></DIV> <DIV><SPAN class=3D184032009-07062002><FONT face=3DTahoma = color=3D#0000ff=20 size=3D2>Sridhar</FONT></SPAN></DIV> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"> <DIV></DIV> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr = align=3Dleft><FONT=20 face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> = Anderson, John=20 [mailto:debbie17@example.org] <BR><B>Sent:</B> Friday, June 07, 2002 = 2:39=20 PM<BR><B>To:</B> 'debbie17@example.org'<BR><B>Subject:</B> RE: = Modifying schema validation<BR><BR></FONT></DIV> <P><FONT size=3D2>Mark,</FONT> </P> <P><FONT size=3D2>If you're doing a lot of this, it is probably worth = looking at=20 schematron, a schema language which supports co-constraints. The = syntax is=20 simple and you can embed schematron instructions in your appinfo = elements in=20 the schema. This allows you to declare this stuff = declaratively.</FONT></P> <P><FONT size=3D2>There are a few validators around which support = embedded=20 schematron, and hopefully this is somethign which will be plugged into = Xerces=20 in the not too distant future. </FONT></P> <P><FONT size=3D2>John</FONT> </P> <P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT = size=3D2>From: Mark=20 Woon [<A=20 = href=3D"mailto:debbie17@example.org">mailto:debbie17@example.org= U</A>]</FONT>=20 <BR><FONT size=3D2>Sent: 06 June 2002 00:17</FONT> <BR><FONT = size=3D2>To:=20 debbie17@example.org</FONT> <BR><FONT size=3D2>Subject: = Modifying schema=20 validation</FONT> </P><BR> <P><FONT size=3D2>Hello...</FONT> </P> <P><FONT size=3D2>I've just started playing with Xerces, and I'm = trying to=20 figure out how </FONT><BR><FONT size=3D2>to hook into the schema=20 validator.&nbsp; In particular, I'm interested in </FONT><BR><FONT=20 size=3D2>adding new constraints for my own work so that I can define=20 dependencies </FONT><BR><FONT size=3D2>(eg. element a is required if = element b=20 is not specified, element a is </FONT><BR><FONT size=3D2>only required = if=20 attribute x is not present, etc.) in my schema.</FONT> </P> <P><FONT size=3D2>Can anyone point me in the right direction?</FONT> = </P> <P><FONT size=3D2>Thanks,</FONT> <BR><FONT size=3D2>-Mark</FONT> = </P><BR><BR> <P><FONT=20 = size=3D2>----------------------------------------------------------------= -----</FONT>=20 <BR><FONT size=3D2>To unsubscribe, e-mail:=20 debbie17@example.org</FONT> <BR><FONT size=3D2>For = additional commands, e-mail: debbie17@example.org</FONT> = </P> <P><I><FONT size=3D2>The information transmitted by this e-mail = message is=20 intended solely for the use of the person to whom or entity to which = it is=20 addressed. The message may contain information that is privileged and=20 confidential.&nbsp; Disclosure, dissemination, distribution, review,=20 retransmission to, other use of or taking any action in reliance upon = this=20 information by anyone other than the intended recipient is prohibited. = If you=20 are not the intended recipient, please do not disseminate, distribute = or copy=20 this communication, by e-mail or otherwise. Instead, please notify us=20 immediately by return e-mail (including the original message with your = reply)=20 and then delete and discard all copies of the message.</FONT></I></P> <P><I><FONT size=3D2>Although we have taken precautions to minimize = the risk of=20 transmitting viruses we nevertheless advise you to carry out your own = virus=20 checks on any attachment to this message. We accept no liability for = any loss=20 or damage caused by viruses.</FONT></I></P></BLOCKQUOTE></BODY></HTML> =00 ------_=_NextPart_001_01C20E04.CF7F5D21-- ------=_NextPartTM-000-68ec3ac5-9ab7-4a30-bf52-a60a12f047ad Content-Type: text/plain; charset=us-ascii --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org ------=_NextPartTM-000-68ec3ac5-9ab7-4a30-bf52-a60a12f047ad-- From xerces-j-debbie17@example.org Fri Jun 07 14:02:16 2002 Return-Path: <xerces-j-debbie17@example.org> Delivered-To: debbie17@example.org Received: (qmail 45198 invoked by uid 500); 7 Jun 2002 14:02:15 -0000 Mailing-List: contact debbie17@example.org; run by ezmlm Precedence: bulk Reply-To: debbie17@example.org list-help: <mailto:debbie17@example.org> list-unsubscribe: <mailto:debbie17@example.org> list-post: <mailto:debbie17@example.org> Delivered-To: mailing list debbie17@example.org Received: (qmail 45188 invoked from network); 7 Jun 2002 14:02:15 -0000 Message-ID: <debbie17@example.org> From: Mark Feblowitz <debbie17@example.org> To: "'debbie17@example.org'" <debbie17@example.org> Subject: RE: Modifying schema validation Date: Fri, 7 Jun 2002 10:02:15 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C20E2B.EDD188B0" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C20E2B.EDD188B0 Content-Type: text/plain; charset="iso-8859-1" John - Something that I've asked around about but have not yet had time to pursue myself: getting Xalan to both validate the incoming XML doc against its respective schema *and* having it apply Schematron constraints, within the context of a single parse. Is this something that you've been able to do? Mark -----Original Message----- From: Anderson, John [mailto:debbie17@example.org] Sent: Friday, June 07, 2002 5:09 AM To: 'debbie17@example.org' Subject: RE: Modifying schema validation Mark, If you're doing a lot of this, it is probably worth looking at schematron, a schema language which supports co-constraints. The syntax is simple and you can embed schematron instructions in your appinfo elements in the schema. This allows you to declare this stuff declaratively. There are a few validators around which support embedded schematron, and hopefully this is somethign which will be plugged into Xerces in the not too distant future. John -----Original Message----- From: Mark Woon [ mailto:debbie17@example.org <mailto:debbie17@example.org> ] Sent: 06 June 2002 00:17 To: debbie17@example.org Subject: Modifying schema validation Hello... I've just started playing with Xerces, and I'm trying to figure out how to hook into the schema validator. In particular, I'm interested in adding new constraints for my own work so that I can define dependencies (eg. element a is required if element b is not specified, element a is only required if attribute x is not present, etc.) in my schema. Can anyone point me in the right direction? Thanks, -Mark --------------------------------------------------------------------- To unsubscribe, e-mail: debbie17@example.org For additional commands, e-mail: debbie17@example.org The information transmitted by this e-mail message is intended solely for the use of the person to whom or entity to which it is addressed. The message may contain information that is privileged and confidential. Disclosure, dissemination, distribution, review, retransmission to, other use of or taking any action in reliance upon this information by anyone other than the intended recipient is prohibited. If you are not the intended recipient, please do not disseminate, distribute or copy this communication, by e-mail or otherwise. Instead, please notify us immediately by return e-mail (including the original message with your reply) and then delete and discard all copies of the message. Although we have taken precautions to minimize the risk of transmitting viruses we nevertheless advise you to carry out your own virus checks on any attachment to this message. We accept no liability for any loss or damage caused by viruses. ------_=_NextPart_001_01C20E2B.EDD188B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <html xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <meta name=3DProgId content=3DWord.Document> <meta name=3DGenerator content=3D"Microsoft Word 9"> <meta name=3DOriginator content=3D"Microsoft Word 9"> <link rel=3DFile-List href=3D"cid:debbie17@example.org"> <title>RE: Modifying schema validation</title> <!--[if gte mso 9]><xml> <o:OfficeDocumentSettings> <o:DoNotRelyOnCSS/> </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml> <w:WordDocument> <w:Zoom>0</w:Zoom> <w:DocumentKind>DocumentEmail</w:DocumentKind> <w:EnvelopeVis/> </w:WordDocument> </xml><![endif]--> <style> <!-- /* Font Definitions */ @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:553679495 8005871587 8 0 66047 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:blue; text-decoration:underline; text-underline:single;} p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig {margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} p {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} span.EmailStyle18 {mso-style-type:personal-reply; mso-ansi-font-size:10.0pt; mso-ascii-font-family:Arial; mso-hansi-font-family:Arial; mso-bidi-font-family:Arial; color:navy;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style> </head> <body lang=3DEN-US link=3Dblue vlink=3Dblue = style=3D'tab-interval:.5in'> <div class=3DSection1> <p class=3DMsoNormal><span class=3DEmailStyle18><font size=3D2 = color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>J= ohn &#8211; <o:p></o:p></span></font></span></p> <p class=3DMsoNormal><span class=3DEmailStyle18><font size=3D2 = color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><= ![if = !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>= <p class=3DMsoNormal><span class=3DEmailStyle18><font size=3D2 = color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>S= omething that I've asked around about but have not yet had time to pursue = myself: getting Xalan to both validate the incoming XML doc against its = respective schema *<b><span style=3D'font-weight:bold'>and</span></b>* having it = apply Schematron constraints, within the context of a single parse. Is this something = that you've been able to do?<o:p></o:p></span></font></span></p> <p class=3DMsoNormal><span class=3DEmailStyle18><font size=3D2 = color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><= ![if = !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>= <p class=3DMsoNormal><span class=3DEmailStyle18><font size=3D2 = color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'>M= ark<o:p></o:p></span></font></span></p> <p class=3DMsoNormal><span class=3DEmailStyle18><font size=3D2 = color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><= ![if = !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>= <p class=3DMsoNormal><span class=3DEmailStyle18><font size=3D2 = color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial'><= ![if = !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>= <p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 = color=3Dblack face=3DTahoma><span = style=3D'font-size:10.0pt;font-family:Tahoma;color:black'>-----Original Message-----<br> <b><span style=3D'font-weight:bold'>From:</span></b> Anderson, John [mailto:debbie17@example.org]<br> <b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, June 07, = 2002 5:09 AM<br> <b><span style=3D'font-weight:bold'>To:</span></b> = 'debbie17@example.org'<br> <b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Modifying = schema validation</span></font></p> <p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 = face=3D"Times New Roman"><span style=3D'font-size:12.0pt'><![if = !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></p> <p style=3D'margin-left:.5in'><font size=3D2 color=3Dblack = face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>Mark,</span></font><font = color=3Dblack><span style=3D'color:black'> </span></font><font color=3Dblack><span = style=3D'color:black; mso-color-alt:windowtext'><o:p></o:p></span></font></p> <p style=3D'margin-left:.5in'><font size=3D2 color=3Dblack = face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>If you're doing a lot of this, = it is probably worth looking at schematron, a schema language which supports co-constraints. The syntax is simple and you can embed schematron = instructions in your appinfo elements in the schema. This allows you to declare this = stuff declaratively.</span></font><font color=3Dblack><span = style=3D'color:black; mso-color-alt:windowtext'><o:p></o:p></span></font></p> <p style=3D'margin-left:.5in'><font size=3D2 color=3Dblack = face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>There are a few validators = around which support embedded schematron, and hopefully this is somethign which will = be plugged into Xerces in the not too distant future. </span></font><font color=3Dblack><span = style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>= </p> <p style=3D'margin-left:.5in'><font size=3D2 color=3Dblack = face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>John</span></font><font = color=3Dblack><span style=3D'color:black'> </span></font><font color=3Dblack><span = style=3D'color:black; mso-color-alt:windowtext'><o:p></o:p></span></font></p> <p style=3D'margin-left:.5in'><font size=3D2 color=3Dblack = face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>-----Original = Message-----</span></font><font color=3Dblack><span style=3D'color:black'> <br> </span></font><font size=3D2 color=3Dblack><span = style=3D'font-size:10.0pt; color:black'>From: Mark Woon [<a = href=3D"mailto:debbie17@example.org">mailto:debbie17@example.org= DU</a>]</span></font><font color=3Dblack><span style=3D'color:black'> <br> </span></font><font size=3D2 color=3Dblack><span = style=3D'font-size:10.0pt; color:black'>Sent: 06 June 2002 00:17</span></font><font = color=3Dblack><span style=3D'color:black'> <br> </span></font><font size=3D2 color=3Dblack><span = style=3D'font-size:10.0pt; color:black'>To: debbie17@example.org</span></font><font = color=3Dblack><span style=3D'color:black'> <br> </span></font><font size=3D2 color=3Dblack><span = style=3D'font-size:10.0pt; color:black'>Subject: Modifying schema validation</span></font><font color=3Dblack><span style=3D'color:black'> </span></font><font = color=3Dblack><span style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>= </p> <p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 = color=3Dblack face=3D"Times New Roman"><span = style=3D'font-size:12.0pt;color:black'><![if !supportEmptyParas]>&nbsp;<= ![endif]></span></font><font color=3Dblack><span = style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>= </p> <p style=3D'margin-left:.5in'><font size=3D2 color=3Dblack = face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>Hello...</span></font><font = color=3Dblack><span style=3D'color:black'> </span></font><font color=3Dblack><span = style=3D'color:black; mso-color-alt:windowtext'><o:p></o:p></span></font></p> <p style=3D'margin-left:.5in'><font size=3D2 color=3Dblack = face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>I've just started playing with = Xerces, and I'm trying to figure out how </span></font><font color=3Dblack><span style=3D'color:black'><br> </span></font><font size=3D2 color=3Dblack><span = style=3D'font-size:10.0pt; color:black'>to hook into the schema validator.&nbsp; In particular, = I'm interested in </span></font><font color=3Dblack><span = style=3D'color:black'><br> </span></font><font size=3D2 color=3Dblack><span = style=3D'font-size:10.0pt; color:black'>adding new constraints for my own work so that I can = define dependencies </span></font><font color=3Dblack><span = style=3D'color:black'><br> </span></font><font size=3D2 color=3Dblack><span = style=3D'font-size:10.0pt; color:black'>(eg. element a is required if element b is not specified, = element a is </span></font><font color=3Dblack><span style=3D'color:black'><br> </span></font><font size=3D2 color=3Dblack><span = style=3D'font-size:10.0pt; color:black'>only required if attribute x is not present, etc.) in my = schema.</span></font><font color=3Dblack><span style=3D'color:black'> </span></font><font = color=3Dblack><span style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>= </p> <p style=3D'margin-left:.5in'><font size=3D2 color=3Dblack = face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>Can anyone point me in the right direction?</span></font><font color=3Dblack><span = style=3D'color:black'> </span></font><font color=3Dblack><span = style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>= </p> <p style=3D'margin-left:.5in'><font size=3D2 color=3Dblack = face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>Thanks,</span></font><font = color=3Dblack><span style=3D'color:black'> <br> </span></font><font size=3D2 color=3Dblack><span = style=3D'font-size:10.0pt; color:black'>-Mark</span></font><font color=3Dblack><span = style=3D'color:black'> </span></font><font color=3Dblack><span = style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>= </p> <p class=3DMsoNormal = style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom: 12.0pt;margin-left:.5in'><font size=3D3 color=3Dblack face=3D"Times New = Roman"><span style=3D'font-size:12.0pt;color:black'><![if = !supportEmptyParas]>&nbsp;<![endif]></span></font><font color=3Dblack><span = style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>= </p> <p style=3D'margin-left:.5in'><font size=3D2 color=3Dblack = face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>---------------------------------= ------------------------------------</span></font><font color=3Dblack><span style=3D'color:black'> <br> </span></font><font size=3D2 color=3Dblack><span = style=3D'font-size:10.0pt; color:black'>To unsubscribe, e-mail: = debbie17@example.org</span></font><font color=3Dblack><span style=3D'color:black'> <br> </span></font><font size=3D2 color=3Dblack><span = style=3D'font-size:10.0pt; color:black'>For additional commands, e-mail: = debbie17@example.org</span></font><font color=3Dblack><span style=3D'color:black'> </span></font><font = color=3Dblack><span style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>= </p> <p style=3D'margin-left:.5in'><i><font size=3D2 color=3Dblack = face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black;font-style:italic'>The = information transmitted by this e-mail message is intended solely for the use of = the person to whom or entity to which it is addressed. The message may contain = information that is privileged and confidential.&nbsp; Disclosure, dissemination, distribution, review, retransmission to, other use of or taking any = action in reliance upon this information by anyone other than the intended = recipient is prohibited. If you are not the intended recipient, please do not = disseminate, distribute or copy this communication, by e-mail or otherwise. Instead, = please notify us immediately by return e-mail (including the
{'source': 'Apache Software Foundation Public Mail Archives'}