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] Type-assignement requirements from Jonathan Robie

John Cowan suggested:

> "MURATA Makoto (FAMILY Given)" scripsit:
> > > The main requirement is to provide type annotations for every element
> > > attribute, perhaps in a separate process from validation.
> I think this is most simply provided with an attribute annotation,
> or the like, which is allowed on element and attribute patterns, and whose
> value is a QName.

The question I have is "What does the QName resolve to?". Does it make sense
to say that the name on its own is sufficient, or must we require that it
references something that contains a formal definition of the type?

Martin Bryan

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

Powered by eList eXpress LLC