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


Help: OASIS Mailing Lists Help | MarkMail Help

relax-ng message

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

Subject: Fallback mechanism for the datatype

Several strawman proposals...

1. Probably the easiest way is to treat unknown datatypes as strings.


<data type="foo" datatypeLibrary="my:secret:datatype:library"/>

would be handled as

<data type="string" datatypeLibrary=""/>

after a warning or such.

Also, it would be nice if any valid document is accepted in the fallback
mode. (We can't help but accept invalid documents)

To achieve that, we just need to abandon key/keyref check for
unavailable datatypes.

2. Allow explicit fallback specification just like XSLT:

<data type="countryCode" datatypeLibrary="dynamic:repository:lookup:ccode">
    <data type="token"

Maybe too cumbersome.

Kohsuke KAWAGUCHI                          +1 650 786 0721
Sun Microsystems                   kohsuke.kawaguchi@sun.com

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

Powered by eList eXpress LLC