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


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: The XML spec in XML: missing tags

[ Lists Home | Date Index | Thread Index ]
  • From: "Eve L. Maler" <elm@arbortext.com>
  • To: "Xml-Dev" <xml-dev@ic.ac.uk>
  • Date: Tue, 24 Feb 1998 19:27:43 -0500

As the maintainer of the specification DTD, let me say thanks for your

At 11:49 AM 2/23/98 -0500, Michael Kay wrote:
>Some comments on the XML tagging in the BNF rules:
>- it is useful to have the non-terminals tagged, though the way in which it
>done is a little clumsy, since the internal identifier and the visible name
>of the non-terminal are necessarily in a one-to-one correspondence. The way
>it is done seems designed primarily to enable a particular translation to

Are you saying that it's clumsy because the element content is duplicated
in the attribute value?  Since the XML is transformed into HTML, it would
actually have been easier to let the content serve as the address (and be
stuffed into both the final <a> element content and its href attribute,
with "#" and "-nt" tacked on).  Alternatively, the element could have been
empty, and its attribute value both used as an address and rendered (with
some transformation that probably isn't worth doing...).  Either way,
nothing would be duplicated in the source.  However, it would make me a
little uncomfortable treating the same string as having two functions.

>- it is a shame that there is no tagging to distinguish terminal symbols
>from metasymbols, since this would enable nicer renditions of the rules,
>e.g. exploiting colour, without having to parse the BNF

I'll take this up with the other editors using the DTD.

>- it would seem more logical for each rule to have a single <rhs>, with any
><vc> and <wfc> constraints being embedded within the <rhs>, rather than
>these being separate elements interspersed among multiple <rhs> elements.

We had a lengthy discussion of whether our production markup should be more
semantic and less presentational.  It's so much work to make the markup
simulate the EBNF and to make the filters handle this, that we decided not
to go further in that direction.  I do agree that the production markup is
less than "pure" in this area.


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


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

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