W3C home > Mailing lists > Public > w3c-sgml-wg@w3.org > June 1997

Re: Update on namespaces

From: Terry Allen <tallen@sonic.net>
Date: Tue, 10 Jun 1997 20:24:11 -0700
Message-Id: <199706110324.UAA01789@bolt.sonic.net>
To: paul@arbortext.com, w3c-sgml-wg@w3.org
What Paul said.  If it's name spaces that are desired, the *sole acceptable
solution for the Internet* in light of current development work is URNs.
A prototype implementation for the name space for RFCs (more complex than
you might think) is currently in draft stage.  

If some other approach to whatever the real problem is is desired,
*please* write up a formal list of requirements couched in language
of appropriate technical complexity *and* construct a document describing
scenarios in which the desired functionality is to be used.  All else,
especially via email, is a waste of time.

Regards,

  Terry Allen    Electronic Publishing Consultant    tallen[at]sonic.net
                   http://www.sonic.net/~tallen/
    Davenport and DocBook:  http://www.ora.com/davenport/index.html
          T.A. at Passage Systems:  terry.allen[at]passage.com 


From w3c-sgml-wg-request@w3.org Tue Jun 10 12:10:57 1997
Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by sub.sonic.net (8.8.5/8.8.5) with ESMTP id MAA11061 for <tallen@sonic.net>; Tue, 10 Jun 1997 12:10:56 -0700
X-envelope-info: <w3c-sgml-wg-request@w3.org>
Received: by www19.w3.org (8.8.5/8.6.12) id PAA16551; Tue, 10 Jun 1997 15:09:22 -0400 (EDT)
Resent-Date: Tue, 10 Jun 1997 15:09:22 -0400 (EDT)
Resent-Message-Id: <199706101909.PAA16551@www19.w3.org>
X-Authentication-Warning: www10.w3.org: Host orchard.arbortext.com [192.86.159.112] claimed to be arbortext.com
Message-Id: <3.0.32.19970610140658.0069bd3c@pophost.arbortext.com>
X-Sender: pbg@pophost.arbortext.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Tue, 10 Jun 1997 14:08:03 -0500
To: w3c-sgml-wg@w3.org
From: Paul Grosso <paul@arbortext.com>
Subject: Re: Update on namespaces
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-List-URL: http://www.w3.org/pub/WWW/Archives/Public/w3c-sgml-wg/
X-See-Also: http://www.w3.org/pub/WWW/MarkUp/SGML/Activity
Resent-From: w3c-sgml-wg@w3.org
X-Mailing-List: <w3c-sgml-wg@w3.org> archive/latest/5011
X-Loop: w3c-sgml-wg@w3.org
Sender: w3c-sgml-wg-request@w3.org
Resent-Sender: w3c-sgml-wg-request@w3.org
Precedence: list
Status: R

I've read Martin's and Andrew's replies, but I'm using Jon's
message as the base for my comments.

I'm not sure I see the need to discuss behavior or even "meaning"
at all with respect to namespaces.  While a DTD (or namespace)
can include (usually non-machine-readable) semantic information,
that isn't standardized and doesn't need to be part of the
standardized solution to XML namespaces at least for the first
pass as far as I see it.  For me, the namespace issue is more
just how to indicate for any (element or maybe attribute) name
from what DTD/namespace it comes.

At 23:06 1997 06 09 -0700, Jon Bosak wrote:
>In order to better understand the requirements for namespaces, several
>members of the SGML ERB met in phone conference with key participants
>in the PICS-NG effort last Friday.  We didn't get through all the
>issues in the time available, but we did arrive at some important
>preliminary understandings.  There seemed to be general agreement on
>the following:
>
>1. One workable way to universally disambiguate the names of elements
>is to associate them somehow with specific URIs.  Not everyone agrees
>that this is the best way -- some of us would prefer a mechanism like
>the SGML formal public identifier -- but there seems to be a general
>acknowledgement that it will work.

I like to think of the "namespaceid" that (per some syntactic suggestions)
might precede the gi name (with a colon separator) as a sort of notation
name.  Then, a declaration such as:
	<!NOTATION namespaceid SYSTEM "...{URI or FSI}..."
or
	<!NOTATION namespaceid PUBLIC "...{FPI}..."
(to show it using 8879 syntax, though the same thing could be accomplished
using other syntaxes) would map the namespaceid into the namespace. Given
that FSIs can point to an or group of storage identifiers, that would seem
to give us the "pointing to multiple namespaces" capability.


>
>4. As indicated in the example just given, it is necessary to be able
>to get more than one category of "meaning" about a given element.
>These different semantic axes may have to come from different places.
>For example, in <birthday>19850527</birthday> it may be necessary to
>point to one specification in order to indicate that the content
>refers to someone's date of birth and to a different specification to
>indicate that content happens in this case to be in ISO format.  This
>is multiple inheritance, but of a kind that can apparently be dealt
>with simply by providing the ability to attach multiple namespace
>identifiers to a given element.

I see no need to semantic axes to the namespace issue.  I don't see
why semantics can't be orthogonal to the "from which DTD(s) or other-specified
set(s) of declarations did this name come" question.

paul
Received on Tuesday, 10 June 1997 23:23:35 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 10:04:40 EDT