Naming Rules

[Portillo, Christina]

Reply to Chris Maden:
Thank you for your excellent pointer to an online ISO 8879. It would be
excellent if a similar thing could be done using the limitations and
expansions to the tagging ruleset defined by XML.

The question probably needs the more clarification in order for an
answer to be put forth.
	dash=45 
	full-stop=46
	colon=58 
	[A-Z]=65-90 
	underscore=95  
	[a-z]=97-122
In the XML SGML Declaration:
		NAMING
		     LCNMSTRT ""
		     UCNMSTRT ""
		     NAMESTRT
		     58 95 192-214 216-246 248-305 308-318 321-328
		     .....snip.....

		     LCNMCHAR ""
		     UCNMCHAR ""
		     NAMECHAR
		     45-46 183 720-721 768-837 864-865 903 1155-1158
		     ....snip....

		     NAMECASE
		     GENERAL NO
		     ENTITYNO

The values for upper case A-Z and lower case a-z are not explicitly
defined for NAMESTRT or NAMECHAR. I assume a default.

The values for underscore and colon are not defined in NAMECHAR. I see
nothing that would lead to assume a default for these values for
NAMECHAR. As I see nothing that would lead me to assume a default for
dash and period in NAMESTRT.

The Extended Naming Rules (http://www.sil.org/sgml/wg8N1896rev.html)
does not indicate the values for NAMECHAR and NAMESTRT are the same. In
fact it appears to me, that the range or character must be specified or
the characters are not an extended naming value for NAMECHAR or
NAMESTRT.

     NAMESTRT 
          means that each character identified by the extended naming
value (if any) has the same
          effect as a character appearing in both UCNMSTRT and LCNMSTRT.

     NAMECHAR 
          means that each character identified by the extended naming
value (if any) has the same
          effect as a character appearing in both UCNMCHAR and LCNMCHAR.


	[189] naming rules =
	      "NAMING", ps+,
	      "LCNMSTRT", (ps+, extended naming value)+, ps+,
	      "UCNMSTRT", (ps+, extended naming value)+, ps+,
	      ("NAMESTRT", (ps+, extended naming value)+, ps+)?,
	      "LCNMCHAR", (ps+, extended naming value)+, ps+,
	      "UCNMCHAR", (ps+, extended naming value)+, ps+,
	      ("NAMECHAR", (ps+, extended naming value)+, ps+)?,
	      "NAMECASE", ps+,
	      "GENERAL", ps+, ("NO"| "YES"), ps+,
	      "ENTITY", ps+, ("NO"| "YES")
	[189.1] extended naming value = parameter literal | character
number | character range
	[189.2] character range = character number, ps*, minus, ps*,
character number 

Does this adequately detail the issue I am trying to resolve? Can you
clarify this for me?

Christina Portillo   
Product Definition and Image Technology

The Boeing Company               Phone: 425.237.3351
PO Box 3707   M/S 6H-AF       Fax:     425.237.3428
Seattle, WA  98124-2207         christina.portillo at boeing.com

> ----------
> From: 	Chris Maden[SMTP:crism at oreilly.com]
> Reply To: 	Chris Maden
> Sent: 	Monday, July 27, 1998 11:32 AM
> To: 	xml-dev at ic.ac.uk
> Subject: 	Re: Naming Rules
> 
> [Christina Portillo]
> > I need some clarification on the differences in the naming rules
> > defined in the XML SGML Declaration and the Naming Rules defined in
> > XML Part 1 Names and Tokens.
> 
> [...]
> 
> > My understanding of the Name restricts the 1st character position to
> > a letter or a underscore or colon which is in sync with the SGML
> > Declaration. But the NameChar allows underscores and colons in the
> > remaining character positions which is at variance with the naming
> > rules defined by the SGML Declaration.
> > 
> > Can you clarify this for me?
> 
> Characters defined as NAMESTRT, LCNMSTRT, or UCNMSTRT are usable as
> name characters; that is, name start characters are a strict subset of
> name characters, and so definition as the former implies definition as
> the latter.
> 
> The relevant productions from ISO 8879 are:
> 
>    [52] name character =
>           name start character |
>           Digit |
>           LCNMCHAR |
>           UCNMCHAR 
>           
>    [53] name start character =
>           LC Letter |
>           UC Letter |
>           LCNMSTRT |
>           UCNMSTRT 
> 
> (See <URL:http://www.oreilly.com/people/staff/crism/sgmldefs.html>.)
> 
> Note that this information is not necessary to understand the XML
> Recommendation; the name productions in REC-XML are correct as they
> stand.
> 
> -Chris
> -- 
> <!NOTATION SGML.Geek PUBLIC "-//Anonymous//NOTATION SGML Geek//EN">
> <!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
> "<URL>http://www.oreilly.com/people/staff/crism/ <TEL>+1.617.499.7487
> <USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>
> 
> xml-dev: A list for W3C XML Developers. To post,
> mailto:xml-dev at ic.ac.uk
> Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
> To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
> (un)subscribe xml-dev
> To subscribe to the digests, mailto:majordomo at ic.ac.uk the following
> message;
> subscribe xml-dev-digest
> List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
> 

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)