[relaxng-user] MIME type for Relax NG Compact?

MURATA Makoto (FAMILY Given) EB2M-MRT at asahi-net.or.jp
Thu Jan 22 00:02:43 ICT 2004


On Wed, 07 Jan 2004 23:08:56 +0900
"MURATA Makoto (FAMILY Given)" <EB2M-MRT at asahi-net.or.jp> wrote:

> If we can live with the vendor tree (*/vnd.*), it is not so difficult to register 
> a media type.  However, it we would like to use the IETF tree, we need an ISO standard.
> (There are some technical problems such as versioning of the compact syntax.)
> 
> In my understanding, James will create PDAM (proposed draft amendement) for the RELAX NG 
> compact syntax soon.  It will probably become an AM (AMedment) to ISO/IEC 19757-2 next year.

I am writing the FCD for DSDL Part 4, which requires the media type for the RELAX NG compact syntax.

I now feel that we should live with the vendor tree.  I do not think that users will care the 
differences between the IETF tree and the vendor tree.   Although a media type in the vendor 
tree does not even need an RFC, it takes too much time to register one in the IETF tree.  
W3C has been trying without much success.

Here is a strawman.  

Top-level media type: application
Subtype name: vnd.oasis-open.relax-ng.rnc
	Note: vnd.relax-ng.rnc might be better, since (1) it is shorter, (2) the RNC syntax 
	is expected to become an ISO standard, (3) we do not need an endorsement from OASIS.
Required param: none
Optional param: charset
Encoding consideration: 
      This media type MAY be encoded as
      appropriate for the charset and the capabilities of the underlying
      MIME transport.  For 7-bit transports, data in either UTF-8 or
      UTF-16 MUST be encoded in quoted-printable or base64.  For 8-bit
      clean transport (e.g., 8BITMIME[RFC1652] ESMTP or NNTP[RFC0977]),
      UTF-8 is not encoded, but the UTF-16 family MUST be encoded in
      base64.  For binary clean transports (e.g., HTTP[RFC2616]), no
      content-transfer-encoding is necessary.
Security considerations:
  Dereferencing embedded URIs may cause security problems.
Interoperability considerations: none
Published specifications: OASIS RELAX NG compact syntax
Applications: relax ng validators
Additional information:
 magic number: none
 file extension: rnc
 mac file type code: 
 OID: none
Intended Usage:  Common
Other Information/General Comment: 
  When the charset parameter is absent, the procedure shown in A2.1 of the RELAX NG compact syntax 
  spec is used.

Cheers,


-- 
MURATA Makoto (FAMILY Given) <EB2M-MRT at asahi-net.or.jp>




More information about the relaxng-user mailing list