OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Attributes problem: getAttributes and getLength

[ Lists Home | Date Index | Thread Index ]
  • From: Bob Kline <bkline@rksystems.com>
  • To: Pen Chiang <ppc@redix.com>
  • Date: Wed, 7 Jun 2000 00:32:20 -0400 (EDT)

On Tue, 6 Jun 2000, Pen Chiang wrote:

> I am wondering if someone can help me with this problem.  I was using the
> getLength method of the NameNodeMap class to get the attributes from my
> node. I have two problems in using this method. My first problem is that my
> attributes sequence become re-ordered.  Secondly, when the data is not
> there, I cannot get my attributes with the #IMPLIED data definition.
> Here is my DTD for the Header record:
> <!ATTLIST Header	Document_No	CDATA #REQUIRED
> 			Release_No	CDATA #REQUIRED
> 			Type_Qualifier	(A |B)	 #IMPLIED
> 			Qty_Qualifer	CDATA #FIXED "A"
> 			Type_Code	DATA #FIXED "PS">
> My input data:
> <Header Document_No="123" Release_No="001" >
> By using the code listed below, I got these answers:
> <Header Release_No = "001" Document_No = "123" Type_Code"PS" Qty_Qualifer =
> "A">
> I was hoping to generate the following stream,
> <Header  Document_No = "123" Release_No = "001" Type_Qualifier=""
> Qty_Qualifer = "A" Type_Code"PS" >

You're seeing the correct behavior.  Order of attributes is not
guaranteed.  And #IMPLIED really means "optional."  If the attribute
isn't in the original (and it doesn't have a default), then you won't
find a node for it in the tree.

Bob Kline

This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS