W3C home > Mailing lists > Public > public-owl-wg@w3.org > October 2008

mime types for manchester and functional syntax

From: Peter F. Patel-Schneider <pfps@research.bell-labs.com>
Date: Thu, 23 Oct 2008 09:29:55 -0400 (EDT)
Message-Id: <20081023.092955.-1300531106.pfps@research.bell-labs.com>
To: public-owl-wg@w3.org

I propose that we use 
	text/owl-functional charset UTF-8
	text/owl-manchester charset UTF-8
as the mime types that we use for the Functional syntax and the
Manchester syntax.

peter

PS:  Here is what turtle has for is MIME type.  I'll send out messages
with proposed versions for us.


B. Internet Media Type, File Extension and Macintosh File Type
(Normative)

contact:
    Eric Prud'hommeaux
See also:
    How to Register a Media Type for a W3C Specification
    Internet Media Type registration, consistency of use
    TAG Finding 3 June 2002 (Revised 4 September 2002)

The Internet Media Type / MIME Type for Turtle is "text/turtle".

It is recommended that Turtle files have the extension ".ttl" (all
lowercase) on all platforms.

It is recommended that sparql query files stored on Macintosh HFS file
systems be given a file type of "TEXT".

This information that follows has been submitted to the IESG for review,
approval, and registration with IANA.

Type name:
    text
Subtype name:
    turtle
Required parameters:
    None
Optional parameters:
    charset  this parameter may be required when transfering non-ascii
    data across some protocols. If present, the value of charset is
    always UTF-8.
Encoding considerations:
    The syntax of Turtle is expressed over code points in Unicode
    [UNICODE]. The encoding is always UTF-8 [RFC3629].
    Unicode code points may also be expressed using an \uXXXX (U+0 to
    U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a
    hexadecimal digit [0-9A-F]
Security considerations:
    Turtle uses IRIs as term identifiers. Applications interpreting data
    expressed in Turtle sould address the security issues of
    Internationalized Resource Identifiers (IRIs) [RFC3987] Section 8,
    as well as Uniform Resource Identifier (URI): Generic Syntax
    [RFC3986] Section 7.
    Multiple IRIs may have the same appearance. Characters in different
    scripts may look similar (a Cyrillic "" may appear similar to a
    Latin "o"). A character followed by combining characters may have
    the same visual representation as another character (LATIN SMALL
    LETTER E followed by COMBINING ACUTE ACCENT has the same visual
    representation as LATIN SMALL LETTER E WITH ACUTE). Any person or
    application that is writing or interpreting data in Turtle must take
    care to use the IRI that matches the intended semantics, and avoid
    IRIs that make look similar. Further information about matching of
    similar characters can be found in Unicode Security Considerations
    [UNISEC] and Internationalized Resource Identifiers (IRIs) [RFC3987]
    Section 8. 
Interoperability considerations:
    There are no known interoperability issues.
Published specification:
    This specification.
Applications which use this media type:
    No widely deployed applications are known to use this media type. It
    may be used by some web services and clients consuming their data.
Additional information:
Magic number(s):
    Turtle documents may have the strings '@prefix' or '@base' (case
    dependent) near the beginning of the document.
File extension(s):
    ".ttl"
Base URI:
    The Turtle '@base <IRIref>' term can change the current base URI for
    relative IRIrefs in the query language that are used sequentially
    later in the document.
Macintosh file type code(s):
    "TEXT"
Person & email address to contact for further information:
    Eric Prud'hommeaux <eric@w3.org>
Intended usage:
    COMMON
Restrictions on usage:
    None
Author/Change controller:
    The Turtle specification is the product of David Beckett and Tim
    Berners-Lee. A W3C Working Group may assume maintenance of this
    document; W3C reserves change control over this specifications. 
Received on Thursday, 23 October 2008 13:30:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 23 October 2008 13:30:57 GMT