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

 


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-spec-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Public Comment


Comment from: ksankara@webmethods.com

Name: Karthick Sankarachary
Title: Lead Engineer
Organization: webMethods, Inc.
Regarding Specification: UDDI V3.0

Correct me if I'm wrong, but by the looks of the latest specification, it is not possible to define a hierarchy of categories, or to be more precise, a taxonomy. 

I can't really use derived categories to represent  a hierarchy, because by definition, the categories in a taxonomy may and will be unrelated to each other.

To illustrate my use case, please take a look see at the taxonomy at http://www.rarespecies.org.na/InfoSys/IMAGES/buffalo/Taxonomy.gif.

I think our best bet is keyedRefereceGroup. Unfortunately, it is not recursive and only allows for one level of nesting of categories, by virtue of the fact that a keyedReferenceGroup cannot contain another keyedReferenceGroup.

So, that begs the question, would it at all be possible to change the type of keyedReferenceGroup like so:

<xsd:complexType name="keyedReferenceGroup" final="restriction">
		<xsd:sequence minOccurs="0" maxOccurs="unbounded">
                  <xsd:choice>
			<xsd:element ref="uddi:keyedReference"/>
			<xsd:element ref="uddi:keyedReferenceGroup"/>
                  <xsd:choice>
		</xsd:sequence>
		<xsd:attribute name="tModelKey" type="uddi:tModelKey" use="required"/>
	</xsd:complexType>

Best Regards,
Karthick Sankarachary


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]