From what I can understand of the spec: "getMemberTypes()" returns the list of the types in the union declaration. At least this is what is currently being returned...
"getItemType()" should instead return the actual validated type of the particular instance of the elements of the list. Cheers, - Fabio On Friday, June 14, 2002, at 08:01 PM, [EMAIL PROTECTED] wrote: > XSSimpleTypeDefinition has a method "getItemType()", which returns another > XSSimpleTypeDefinition, the item type of a list type. Another method > "getMemberTypes()" returns a list of XSSimpleTypeDefinition's, the member > types of a union type. > > By calling these two methods, I believe you can get what you are looking > for. Of course, "getVariety()" should be called before these two methods > to > make sure that it is a list or union type. > > Cheers, > Sandy Gao > Software Developer, IBM Canada > (1-905) 413-3255 > [EMAIL PROTECTED] > > > > > Fabio Riccardi > <[EMAIL PROTECTED] To: [EMAIL PROTECTED] > org > m> cc: > Subject: XSListSimpleType > missing [was: [PSVI] full support is > 06/14/2002 available] > 09:57 PM > Please respond > to > xerces-j-dev > > > > > > Hi, > > I'm using the PSVI interfaces and everything seems to work fine, except > that there is no way to access the individual item type(s) for a list. > This is quite annoying for lists of union types. > > In a future release would it be possible to add something like > XSListSimpleType as defined by: > > http://lists.w3.org/Archives/Member/w3c- > archive/2001Apr/att-0138/01-xml-schema-cm- > api.html#SchemaCM-XSListSimpleType > > Regards, > > - Fabio > > On Monday, June 3, 2002, at 06:16 AM, [EMAIL PROTECTED] wrote: > >> 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 >> (1-905) 413-3255 >> [EMAIL PROTECTED] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
