XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] From Pox to Pojo

Andrew Welch writes:

> <xs:annotation>
>         <xs:documentation>Not Applicable</xs:documentation>
> 
> My ideal enum is something like:
> 
> Item.Not_Applicable

Obviously you're free to seek any interface that meets your needs, but I'd 
point out that the schema recommendation [1] gives you two kinds of 
"annotation":

1) <xs:documentation> which "is intended for human consumption"

2) <xs:appinfo> which is intended "for automatic processing"

So, while it's perfectly reasonable to want to see information from 
<xs:documentation> in some API for certain purposes, it's probable that 
<xs:appinfo> is closer to what you would use if you intend schema 
information to be provided to your application.  Of course, that 
immediately leaves you with a question analagous to your original one, 
which is whether your databinding tool provides access to that either. 
FWIW, additional attributes on schema document markup are another source 
of appinfo-like information.

Noah

[1] http://www.w3.org/TR/2004/PER-xmlschema-1-20040318/#Annotation_details

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------






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


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

Copyright 1993-2007 XML.org. This site is hosted by OASIS