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


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Derivation by restriction in XML Schema

[ Lists Home | Date Index | Thread Index ]
  • From: ht@cogsci.ed.ac.uk (Henry S. Thompson)
  • To: "Arnold, Curt" <Curt.Arnold@hyprotech.com>
  • Date: 07 Mar 2000 08:45:45 +0000

"Arnold, Curt" <Curt.Arnold@hyprotech.com> writes:

> >4) You can't restrict material from another namespace, 
> >whether it's attribute or element, unless you own, or 
> >bogusly claim to own, rights to define elements, 
> >attributes, types in that namespace, which, in the 
> >case of the XML namespace, you don't.
> I don't think I buy that.  If I include the xlink:show
> attribute in an element by referencing its attribute
> group from the xlink schema, it would seem appropriate
> for me to say that the default is "replace" or that "embed"
> is prohibited in this context.

Attribute 'equivalence classes' would give you that, and they may yet
make it in to the spec.

  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
          W3C Fellow 1999--2001, part-time member of W3C Team
     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
	    Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
		     URL: http://www.ltg.ed.ac.uk/~ht/

This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS