Re: The role of media types for XML content

"John.Cowan" <jcowan@reutershealth.com> Wed, 15 June 2005 11:53 UTC

Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j5FBrS6B052456; Wed, 15 Jun 2005 04:53:28 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j5FBrSGZ052455; Wed, 15 Jun 2005 04:53:28 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from mail.reutershealth.com ([65.246.141.36]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j5FBrQRV052408 for <ietf-xml-mime@imc.org>; Wed, 15 Jun 2005 04:53:26 -0700 (PDT) (envelope-from jcowan@reutershealth.com)
Received: from skunk.reutershealth.com (mail [65.246.141.36]) by mail.reutershealth.com (8.13.1/8.13.1) with SMTP id j5FBrF0r025782; Wed, 15 Jun 2005 07:53:16 -0400 (EDT)
Received: by skunk.reutershealth.com (sSMTP sendmail emulation); Wed, 15 Jun 2005 07:53:14 -0400
Date: Wed, 15 Jun 2005 07:53:14 -0400
From: "John.Cowan" <jcowan@reutershealth.com>
To: Martin Duerst <duerst@it.aoyama.ac.jp>
Cc: Liam Quin <liam@w3.org>, MURATA Makoto <murata@hokkaido.email.ne.jp>, ietf-xml-mime@imc.org
Subject: Re: The role of media types for XML content
Message-ID: <20050615115313.GA2072@NYCMJCOWA2>
References: <20050614232431.C56F.MURATA@hokkaido.email.ne.jp> <187486099.20050614174033@w3.org> <20050615075541.6960.MURATA@hokkaido.email.ne.jp> <20050614235947.GL1742@w3.org> <6.0.0.20.2.20050615092831.073c7900@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6.0.0.20.2.20050615092831.073c7900@localhost>
User-Agent: Mutt/1.4.2.1i
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

Martin Duerst scripsit:

> Also, Relax NG in XML syntax most probably may have provisions
> of some sort about how to include other namespaces, e.g. for
> documentation,...

Indeed, arbitrary elements and attributes may appear in a RELAX NG document,
provided they are in a namespace other than the RNG namespace.  There is
no specific wrapper element as there is in W3C XML Schema.

The RNG documentation indeed provides for a documentation namespace
as well as a namespace for recording DTD-specific information in order
to make it possible to roundtrip DTDs through RNG.

-- 
"Well, I'm back."  --Sam        John Cowan <jcowan@reutershealth.com>