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: RE: [relax-ng] Some ideas about type-assignment

I like these ideas. If type assignment can be done with an XPath expression,
I take that to mean it will be in an attribute value, and that such
attributes will also belong to a namespace (like
http://relaxng.org/ns/type-assignment/1.0). My question is: Will this
namespace also have elements (a vocabulary), and if so, could you express
type-assignment for a given document in a separate document as well as in an
embedded form?


> -----Original Message-----
> From: Murata Makoto [mailto:EB2M-MRT@asahi-net.or.jp]
> Sent: Sunday, August 11, 2002 7:45 PM
> To: relax-ng@lists.oasis-open.org
> Subject: [relax-ng] Some ideas about type-assignment
> - Type-assignment should be useful for XQuery.
> - Type-assignment should be useful for data binding tools.
> - Type-assignement should be separated from validation (It should be
>   possible to do type-assignment without performing validation, and
>   vice versa)
> - Ideally, deep understanding of the RELAX NG spec (and underlying
>   hedge automata) should not be required for implementing
>   type-assignemnt.  (It might be an idea to create XPath
>   expressions from RELAX NG schemas.)
> - Type-assignment does not have to be possible for every RELAX NG
>   schema.  (When it is not possible, diagnostic message should
>   be issued.)
> - Given a RELAX NG schema and a document, type-assignment should
>   1) uniquely determine the datatype (data/text/value/list) of
>      each string (i.e. attribute values and mixed contents),
>   2) uniquely determine the named pattern for every element,
>   3) uniquely determine which group/interleave/choice is applied
>      to the content of each element and the value of each attribute,
>      and
>   4) do (1) for each token created by <list>, and do (3) for
>      each token sequence
>   5) determine if whitespace is ignorable
>   Note: I am not sure which of them should be adopted.
> - Type-assignment should not impose much burden on schema authors.
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>

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

Powered by eList eXpress LLC