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


Help: OASIS Mailing Lists Help | MarkMail Help



   Namespaces in XML: 3.1 the example [2]

[ Lists Home | Date Index | Thread Index ]
  • From: james anderson <James.Anderson@mecom.mixx.de>
  • To: "xml-dev@ic.ac.uk" <xml-dev@ic.ac.uk>
  • Date: Wed, 01 Apr 1998 01:56:24 +0200

re 3.1 (the o/l bookstore example)

the discussion raises a number of questions

1. when a namespace-pi binds a namespace, is it intended that, should a schema
have been specified, a processor  verify (immediately?, later?, when?) the
existence (the content?) of the specified schema?
   is this a well-formedness or a validity issue?

2. if the schema is present, should the processor permit local additions to the
namespace, that is the introduction of names which are not present in the
external definition?
  should the processor permit redefinition of existing names from the namespace?

if the answer to first is "no", then cross-references are no problem.
if the answer to the second is yes, then it would be possible to place hooks in
a dtd by selective entity placement, which entities the using document/dtd would
be free to (re)define.

(or rather, it's almost possible: there's a small problem, that the wd-standard
precludes qualified entity names. why?)

3. the element definition examples below shouldn't, in any event, appear in the
original schema(s).
while it is ok (and necessary) to constrain the namespace in definition tags in
the internal subset, to do so in the original schema itself would prevent
subsequent users of the dtd from remapping the tags to suit their needs. in
general this is too restrictive.

Chris Smith wrote:

> On Mon, 30 Mar 1998, David Megginson wrote:
> > Chris Smith writes:
> >
> >  > <E:Order>
> >  >   <dsig:dsig>
> >  >     <E:Manifest>80183589575795589189518915</E:Manifest>
> >  >
> >  > My question is simply: what is the definition for "Order" ?
> >
> > You would have to do something like this:
> >
> >   <!ELEMENT E:Order (dsig:dsig, ...)>
> >   <!ELEMENT dsig:dsig (E:Manifest, ...)>
> >   <!ELEMENT E:Manifest (#PCDATA)>
> I must admit I had considered this, but had rejected it since it
> seemed to require that each DTD exist before the other DTD. In
> addition, it hardly seemed reasonable for something as general as
> dsig: to know - in the DTD - about all its uses. (This is why I
> thought that the use of ANY or #PCDATA might be a way to facilitate
> the experiments.)

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