[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Defining non-WXS datatypes

• To: <xml-dev@l...>
• Subject: Re: Defining non-WXS datatypes
• From: "Rick Jelliffe" <ricko@a...>
• Date: Fri, 18 Jul 2003 15:57:29 +1000
• References: <000001c340ce$cba90c00$0100a8c0@picard> <00d201c3414f$698f80e0$4bc8a8c0@A...> <75896655722.20030717202646@j...>

From: "Jeni Tennison" <jeni@j...>

> I thought I'd spend a little time on this, so I've put together a
> "datatype library language". 

I think this is really great: a light at the end of the tunnel, Jeni!

For completeness, I think you might also need to specify a storage mapping: 
this might be like the normalization mapping, but instead of mapping to a string
it maps to an (IDL?) data structure. 

It would make no difference to a validator, but it might be good for data binding
and for markup minimization opportunities.

On the issue of namespaces, I think it is a mistake not to require explicit prefixes
in the XPaths.  I also think it is a mistake to use the namespace context for the
queries: better to make a Chinese wall separating namespaces used by element
and attribute names, and namespaces used by content: this is what Schematron
does and I think it has worked really well.   No prefix should mean no namespace.
It isn't a favour to users for schema languages to provide too much flexibility in this
area (compare with elementFormDefault of WXS ), because the user cannot
tell immediately whether an unprefixed name is in any namespace--one more thing
to worry about when they need to have one fewer thing.  (Forcing no-prefix=no-namespace
and using separate declarations for namespaces does not reduce expresive power.)

Cheers
Rick Jelliffe

• Follow-Ups:
  • Re: Defining non-WXS datatypes
    • From: Jeni Tennison <jeni@j...>

• References:
  • Relax NG annoyances
    • From: "Jimmy Cerra" <jimbolist@h...>
  • Re: Relax NG annoyances
    • From: "Rick Jelliffe" <ricko@a...>
  • Defining non-WXS datatypes
    • From: Jeni Tennison <jeni@j...>

• Prev by Date: Re: Non-deterministic content models
• Next by Date: Re: Defining non-WXS datatypes
• Previous by thread: Defining non-WXS datatypes
• Next by thread: Re: Defining non-WXS datatypes
• Index(es):
  • Date
  • Thread