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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: Another look at namespaces

[ Lists Home | Date Index | Thread Index ]
  • From: "James Tauber" <jtauber@jtauber.com>
  • To: "Simon St.Laurent" <simonstl@simonstl.com>, "XML-Dev Mailing list" <xml-dev@ic.ac.uk>
  • Date: Mon, 20 Sep 1999 16:46:33 +0800

> So we're having problems connecting the signifier 'language' to a meaning
> common across the participants of this list.

Indeed :-)

> The odd notion is of "formal grammars mapping to namespaces", not of
> "formal grammars", which range from useful to utterly useless.  Some of
> them are indeed odd, but it's not 'formal grammar' I'm questioning here.

Oh good.

> >These are all called "grammars". They all define things called
"languages".
> >They are not "grammars" and "languages" the way Noah Webster used those
> >words or the way you seem to use them. They are "grammars" and
"languages"
> >the way computer scientists use those words.
>
> Meaning one grammar + vocabulary -> language? Where the quantities are all
> one?

You don't actually need the "vocabulary". The alphabet of a formal language
is part of the grammar.

> I think in practice you may find multiple grammars used within the
> same language, even a formal one

Ahh. But now you are using "language" in a way other than "the set of
utterances generated by the grammar" right? Unless you mean that sometimes
the same syntactic rules can be expressed two different ways eg

a+

versus

a a*

> and (yuck for some) not just subsets (once you let ANY in the door, it all
goes).  Trying to keep it all
> exclusively singular seems to be a common dream throughout computing, but
> one I hope we can leave behind more and more over time.

Let me stress again, I am not saying you can always have a single grammar
for a particular "language". I am saying that you can have a single grammar
for a particular "formal language in the sense used by Paul".

> I think we might do well to ponder whether XML is really about creating
> formal languages or for encoding information already represented in
natural
> languages.  If it's the latter, the results might be more interesting.

Why can't it be both? Isn't that the whole point of write schemata
(including DTDs)? Isn't it about formalising the encoding of this
information.

James


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/ and on CD-ROM/ISBN 981-02-3594-1
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