W3C home > Mailing lists > Public > xmlschema-dev@w3.org > July 2002

RE: What good is Restriction?

From: Mark Feblowitz <mfeblowitz@frictionless.com>
Date: Wed, 10 Jul 2002 14:31:03 -0400
Message-ID: <4DBDB4044ABED31183C000508BA0E97F040ABD64@fcpostal.frictionless.com>
To: "'Biron,Paul V'" <Paul.V.Biron@kp.org>, "'Eric van der Vlist'" <vdv@dyomedea.com>, Jeff Lowery <jlowery@scenicsoft.com>
Cc: xmlschema-dev@w3.org

Understood. But the basic idea remains the same: identify the affected
element definition by context, apply the restrictions to that element. 

The trouble with using existing Schema syntax/structure and a
restriction/cancellation semantic is that by *not* mentioning a child
element, it's not clear whether it should stay the same or be eliminated.
Then you get into developing a secondary language (more operational in
nature) to describe how the referenced element differs from the original.

Not at all easy.

 -----Original Message-----
From: 	Biron,Paul V [mailto:Paul.V.Biron@kp.org] 
Sent:	Wednesday, July 10, 2002 1:39 PM
To:	'Eric van der Vlist'; Jeff Lowery
Cc:	xmlschema-dev@w3.org
Subject:	RE: What good is Restriction?

> -----Original Message-----
> From:	Eric van der Vlist [SMTP:vdv@dyomedea.com]
> Sent:	Wednesday, July 10, 2002 10:30 AM
> To:	Jeff Lowery
> Cc:	'Biron,Paul V'; xmlschema-dev@w3.org
> Subject:	RE: What good is Restriction?
> On Wed, 2002-07-10 at 19:24, Jeff Lowery wrote:
> > I thought XPaths were suggested as an alternative in this case. Why was
> that
> > rejected? It's used for keydefs.
> They can be a real mess in some cases... for instance if you use
> substitution group to substitute one of the elements on the path!
To elaborate slightly...

Schemas are defined at the component level...not at the XML syntax level.
Thus, XPath's are at the wrong level of representation.

Received on Wednesday, 10 July 2002 14:31:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:15:04 UTC