document appendix for functional syntax MIME type

Here is my initial draft of an appendix to Syntax that has the stuff
needed for the MIME type.  I think that the equivalent for the
Manchester Syntax would be very similar.

peter



Note: Syntax says that functional-style syntax SHOULD use the UTF-8
      encoding.  This needs to be coordinated with this document.
      Turtle *must* be UTF-8.  I suggest we go to requiring (i.e., to
      use MUST) UTF-8.

Note: There are some questions to be answered and possible changes.  See
      "**" below. 


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

Contact:
    ???
** Who should be the contact?  W3C?

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 the OWL Functional Syntax is
"text/owl-functional".

It is recommended that OWL Functional Syntax files have the extension
".owl-fun" (all lowercase) on all platforms.

** Maybe use .ofn and .omn to get to 2-char extensions?

It is recommended that OWL Functional Syntax 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:
    owl-functional
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.  
** See first note above.
Encoding considerations:
    The syntax of the OWL Functional Syntax is expressed over code
    points in Unicode [UNICODE]. The encoding is always UTF-8 [RFC3629].
** See first note above.
Security considerations:
    The OWL Functional Syntax uses IRIs as term identifiers.
    Applications interpreting data expressed in the OWL Functional
    Syntax should address the security issues of Internationalized
    Resource Identifiers (IRIs) [RFC3987] Section 8, as well as Uniform
    Resource Identifiers (URI): Generic Syntax [RFC3986] Section 7.
    Multiple IRIs may have the same appearance. Characters in different
    scripts may look similar (a Cyrillic "o" 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 the OWL
    Functional Syntax must take care to use the IRI that matches the
    intended semantics, and avoid IRIs that may 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.
** Check this.
Additional information:
    None.
Magic number(s):
    OWL Functional Syntax documents may have the strings 'Namespace(' or
    'Ontology(' (case dependent) near the beginning of the document.
File extension(s):
    ".owl-fun"
Base URI:
    There are no constructs in the OWL Functional Syntax to change the
    Base URI.
Macintosh file type code(s):
    "TEXT"
Person & email address to contact for further information:
    ???
** Who??
Intended usage:
    COMMON
Restrictions on usage:
    None
Author/Change controller:
    The OWL Functional Syntax is the product of the W3C OWL Working
    Group; W3C reserves change control over this specification.

Received on Thursday, 23 October 2008 15:14:04 UTC