Re: Issue: shall we rename the name attribute?

[James Clark <jjc@jclark.com>]

This doesn't seem like an improvement to me.

A big difference between RELAX Core and RELAX NG is that with RELAX NG the
names of things you define (which occur within a grammar/module) never occur
in instances: there are no element or attribute declarations.  The only
kinds of name that occur in instances are names of <attribute>s and
<element>s (whether expressed via a name attribute or a name element).
Since elements and attributes are components of instances, but patterns and
parameters are not, I think it is already clear which names correspond to
names in instances and which don't.

Personally I found the name/role/label distinction to be the single most
confusing thing in RELAX Core.  I really don't want to introduce something
similar in RELAX NG.

----- Original Message -----
From: "Murata Makoto" <mura034@attglobal.net>
To: <relax-ng@lists.oasis-open.org>
Sent: Saturday, June 09, 2001 7:56 PM
Subject: Issue: shall we rename the name attribute?


> Some names in a pattern do not appear in instances, but others do.
> At present, the attribute "name" is used for all such names.  I would
> propose to use "name" only for the second camp and introduce new
attributes
> for the first camp.
>
> 1) Occurring in instances
>
> - @name of <attribute>
> - @name of <element>
> - <name> in name-class
>
> 2) Not occurring in instances
>
> - @name of <start>, <define>, <ref>, and <parentRef>
>
> I propose @pattern.
>
> -  @name of param
>
> Hmm.  How about  <set param="....">  ?
>
> Cheers,
>
> Makoto
>
> Internet: mura034@attglobal.net
> Nifty: VEQ00625
>
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: relax-ng-request@lists.oasis-open.org
>
>
>