• From: "Pete Cordell" <petexmldev@c...>
• To: "Costello, Roger L." <costello@m...>,<xml-dev@l...>
• Date: Thu, 4 Dec 2008 14:59:51 -0000

Hi Roger,

The cited document is quite conservative in terms of what suggests avoiding. 
The authors included a number of open source tools, and in this case the 
open source community tends lags behind the commercial community in terms of 
what is supported.  I think this is partly because those tools are built 
with a particular application in mind.

Our don't use list would look something like:

Don't use these XML Schema elements:

<appinfo> - Can't remember what this does, but I don't think we do it
<key>
<keyref>
<notation>
<unique>

Don't use these XML Schema attribute:

@xpath

Don't use these XML Schema datatypes:

ENTITIES
ENTITY
NOTATION

Room for improvement, but not as dire as you originally suggested!

HTH,

Pete Cordell
Codalogic Ltd
Interface XML to C++ the easy way using XML C++
data binding to convert XSD schemas to C++ classes.
Visit http://codalogic.com/lmx/ for more info

----- Original Message ----- 
From: "Costello, Roger L." <costello@m...>
To: <xml-dev@l...>
Sent: Thursday, December 04, 2008 2:08 PM
Subject: RE:  Feasibility of "do all application coding in the XML 
languages"?





Rick Jelliffe wrote:

> "what kinds of XSD structures are unwise or unsafe?"

> http://www.w3.org/TR/xmlschema-patterns/
>
> The gist is in Appendix F

Thanks Rick!

Let me see if I understand correctly:

Want to create an XML Schema that is broadly adopted?

Some of your users will use data binding tools to map the XML Schema 
constructs into data structures in an imperative programming language?

Then don't use any of the XML Schema constructs listed below.

Don't use these XML Schema elements:

<all>
<anyAttribute>
<appinfo>
<attributeGroup>
<choice>
<fractionDigits>
<group>
<key>
<keyref>
<length>
<list>
<maxExclusive>
<maxInclusive>
<maxLength>
<notation>
<pattern>
<redefine>
<simpleContent>
<totalDigits>
<union>
<unique>
<whitespace>

Don't use these XML Schema attribute:

@block
@blockDefault
@default
@final
@finalDefault
@fixed
@itemType
@memberTypes
@processContents
@substitutionGroup
@xpath

Don't use these XML Schema datatypes:

ENTITIES
ENTITY
ID
IDREF
IDREFS
NMTOKEN
NMTOKENS
NOTATION
date
decimal
duration
float
gDay
gMonth
gMonthDay
gYear
gYearMonth
hexBinary
integer
language
negativeInteger
unsignedByte
unsignedInt
unsignedLong
unsignedShort

Do I correctly understand the state of affairs with regard to using data 
binding tools with XML Schema?

/Roger
_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

• References:
  • Feasibility of "do all application coding in the XML languages"?
    • From: "Costello, Roger L." <costello@m...>
  • Re: Feasibility of "do all application coding in the XML languages"?
    • From: "Kurt Cagle" <kurt.cagle@g...>
  • Re: Feasibility of "do all application coding in the XMLlanguages"?
    • From: Rick Jelliffe <rjelliffe@a...>
  • RE: Feasibility of "do all application coding in the XMLlanguages"?
    • From: "Costello, Roger L." <costello@m...>