# $Id: MIMEHeaderPermanentRegistry.n3,v 1.6 2004/04/16 10:41:40 graham Exp $
#
# RDF message header field registry generator data for
# permanent mail header fields
#
#--------+---------+---------+---------+---------+---------+---------+---------+
#
# Copyright (c) 2002, G. KLYNE
# All rights reserved.
#
#--------+---------+---------+---------+---------+---------+---------+---------+
# $Source: /file/cvsdev/HdrRegistry/MIMEHeaderPermanentRegistry.n3,v $
# $Author: graham $
# $Revision: 1.6 $ $Date: 2004/04/16 10:41:40 $
#--------+---------+---------+---------+---------+---------+---------+---------+
#        1         2         3         4         5         6         7         8

@prefix rdf:      <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs:     <http://www.w3.org/2000/01/rdf-schema#> .
@prefix foaf:     <http://xmlns.com/foaf/0.1/> .
@prefix wn:       <http://xmlns.com/wordnet/1.6/> .
@prefix hdr:      <http://id.ninebynine.org/wip/2002/IETF/MsgHdr/> .

# TODO:  use hdr:controller for change-control, distinct from hdr:author


#### MIME ####

<http://id.ninebynine.org/wip/2002/IETF/HeaderField#MIME-Version>
    a hdr:HeaderField ;
    hdr:fieldName "MIME-Version" ;
    hdr:label "MIME version number" ;
    hdr:protocol hdr:Protocol_mime ;
    hdr:status "standards-track" ;
    hdr:author hdr:Author_IETF ;
    hdr:controller hdr:Author_IETF ;
    hdr:specification hdr:RFC2045_4 ;
    hdr:comment
        """An indicator that this message is formatted according to the
           MIME standard, and an indication of which version of MIME is
           utilized.""" .

<http://id.ninebynine.org/wip/2002/IETF/HeaderField#Content-ID>
    a hdr:HeaderField ;
    hdr:fieldName "Content-ID" ;
    hdr:label "Identify content body part" ;
    hdr:protocol hdr:Protocol_mime ;
    hdr:status "standards-track" ;
    hdr:author hdr:Author_IETF ;
    hdr:controller hdr:Author_IETF ;
    hdr:specification hdr:RFC2045_7 ;
    hdr:comment
        """Specifies a Unique ID for one MIME body part of the
           content of a message.""" .

<http://id.ninebynine.org/wip/2002/IETF/HeaderField#Content-Description>
    a hdr:HeaderField ;
    hdr:fieldName "Content-Description" ;
    hdr:label "Description of message body part" ;
    hdr:protocol hdr:Protocol_mime ;
    hdr:status "standards-track" ;
    hdr:author hdr:Author_IETF ;
    hdr:controller hdr:Author_IETF ;
    hdr:specification hdr:RFC2045_8 ;
    hdr:comment
        """Description of a particular body part of a message,
           for example a caption for an image body part.""" .

<http://id.ninebynine.org/wip/2002/IETF/HeaderField#Content-Transfer-Encoding>
    a hdr:HeaderField ;
    hdr:fieldName "Content-Transfer-Encoding" ;
    hdr:label "Content transfer encoding applied" ;
    hdr:protocol hdr:Protocol_mime ;
    hdr:status "standards-track" ;
    hdr:author hdr:Author_IETF ;
    hdr:controller hdr:Author_IETF ;
    hdr:specification hdr:RFC2045_6 ;
    hdr:comment
        """Coding method used in a MIME message body part.""" .

<http://id.ninebynine.org/wip/2002/IETF/HeaderField#Content-Type>
    a hdr:HeaderField ;
    hdr:fieldName "Content-Type" ;
    hdr:label "MIME content type" ;
    hdr:protocol hdr:Protocol_mime ;
    hdr:status "standards-track" ;
    hdr:author hdr:Author_IETF ;
    hdr:controller hdr:Author_IETF ;
    hdr:specification hdr:RFC2045_5 ;
    hdr:comment
        """Format of content (character set etc.) Note that the values
           for this header field are defined in different ways in
           RFC 1049 and in MIME (RFC 2045), look for the 'MIME-version'
           header field to understand if Content-Type is to be
           interpreted according to RFC 1049 or according to MIME.
           The MIME definition should be used in generating mail.
           RFC 1049 has 'historic' status.  RFC 1766 defines a parameter
           'difference' to this header field.
           Various other Content-Type define various additional parameters.
           For example, the parameter 'charset' is mandatory for all
           textual Content-Types.
           See also: RFC 1049,  RFC 1123: 5.2.13,  RFC 1766: 4.1.""" .


#### MHTML ####

<http://id.ninebynine.org/wip/2002/IETF/HeaderField#Content-Base>
    a hdr:HeaderField ;
    hdr:fieldName "Content-Base" ;
    hdr:label "Base to be used for resolving relative URIs within this content part." ;
    hdr:protocol hdr:Protocol_mime ;
    hdr:status "standards-track" ;
    hdr:author hdr:Author_IETF ;
    hdr:controller hdr:Author_IETF ;
    hdr:specification hdr:RFC2110 ;
    hdr:comment
        """Base to be used for resolving relative URIs within this
           content part.  See also Content-Location.
           This header was included in the first version of MHTML and 
           HTTP 1.1 but removed in the second version (RFC2557).
        """.

<http://id.ninebynine.org/wip/2002/IETF/HeaderField#Content-Location>
    a hdr:HeaderField ;
    hdr:fieldName "Content-Location" ;
    hdr:label "URI for retrieving a body part" ;
    hdr:protocol hdr:Protocol_mime ;
    hdr:status "standards-track" ;
    hdr:author hdr:Author_IETF ;
    hdr:controller hdr:Author_IETF ;
    hdr:specification hdr:RFC2557 ;
    hdr:comment
        """URI using which the content of this body-part part was retrieved,
           might be retrievable, or which otherwise gives a globally unique 
           identification of the content.
        """ .


#### Other MIME fields ####

<http://id.ninebynine.org/wip/2002/IETF/HeaderField#Content-features>
    a hdr:HeaderField ;
    hdr:fieldName "Content-features" ;
    hdr:label "Indicates content features of a MIME body part" ;
    hdr:protocol hdr:Protocol_mime ;
    hdr:status "standards-track" ;
    hdr:author hdr:Author_IETF ;
    hdr:controller hdr:Author_IETF ;
    hdr:specification
      [ = <urn:ietf:rfc:2912> ;
        hdr:xref    "RFC2912" ;
        hdr:label   "RFC 2912" ;
        hdr:document <http://www.rfc-editor.org/rfc/rfc2912.txt> ] ;
    hdr:section  "section 3" ;
    hdr:comment """The 'Content-features:' header can be used to annotate
                   a MIME body part with a media feature expression,
                   to indicate features of the body part content.
                   See also: RFC 2533, RFC 2506, RFC 2045.""" .

<http://id.ninebynine.org/wip/2002/IETF/HeaderField#Content-Disposition>
    a hdr:HeaderField ;
    hdr:fieldName "Content-Disposition" ;
    hdr:label "Intended content disposition and file name" ;
    hdr:protocol hdr:Protocol_mime ;
    hdr:status "standards-track" ;
    hdr:author hdr:Author_IETF ;
    hdr:controller hdr:Author_IETF ;
    hdr:specification hdr:RFC2183 ;
    hdr:comment
        """Whether a MIME body part is to be shown inline or is an
           attachment; can also indicate a suggested filename for use
           when saving an attachment to a file.""" .

<http://id.ninebynine.org/wip/2002/IETF/HeaderField#Content-Language>
    a hdr:HeaderField ;
    hdr:fieldName "Content-Language" ;
    hdr:label "Language of message content" ;
    hdr:protocol hdr:Protocol_mime ;
    hdr:status "standards-track" ;
    hdr:author hdr:Author_IETF ;
    hdr:controller hdr:Author_IETF ;
    hdr:specification hdr:RFC3282 ;
    hdr:comment
        """Can include a code for the natural language used in a message,
           e.g. 'en' for English.
           Can also contain a list of languages for a message containing
           more than one language.
        """ .

<http://id.ninebynine.org/wip/2002/IETF/HeaderField#Content-Alternative>
    a hdr:HeaderField ;
    hdr:fieldName "Content-Alternative" ;
    hdr:label "Alternative content available" ;
    hdr:protocol hdr:Protocol_mime ;
    hdr:status "work-in-progress" ;
    hdr:author hdr:Author_GK ;
    hdr:controller hdr:Author_IETF ;
    hdr:specification hdr:RFC3297 ;
    hdr:comment
        """Information about the media features of alternative content
           formats available for the current message.
        """ .

<http://id.ninebynine.org/wip/2002/IETF/HeaderField#Content-MD5>
    a hdr:HeaderField ;
    hdr:fieldName "Content-MD5" ;
    hdr:label "MD5 checksum of content" ;
    hdr:protocol hdr:Protocol_mime ;
    hdr:status "standards-track" ;
    hdr:author hdr:Author_IETF ;
    hdr:controller hdr:Author_IETF ;
    hdr:specification hdr:RFC1864 ;
    hdr:comment
        """Checksum of content to ensure that it has not been modified.""" .

<http://id.ninebynine.org/wip/2002/IETF/HeaderField#Content-Duration>
    a hdr:HeaderField ;
    hdr:fieldName "Content-Duration" ;
    hdr:label "Time duration of content" ;
    hdr:protocol hdr:Protocol_mime ;
    hdr:status "standards-track" ;
    hdr:author hdr:Author_IETF ;
    hdr:controller hdr:Author_IETF ;
    hdr:specification hdr:RFC2424 ;
    hdr:comment
        """Time duration of body part content, in seconds 
           (e.g. for audio message).
        """ .

#--------+---------+---------+---------+---------+---------+---------+---------+
#
# $Log: MIMEHeaderPermanentRegistry.n3,v $
# Revision 1.6  2004/04/16 10:41:40  graham
# Fix status of content disposition header field
#
# Revision 1.5  2004/04/07 15:03:59  graham
# Update report format for XML2RFC output
# Update header field definitions
# Add Charles Lindsey's Netnews header definitions
#
# Revision 1.4  2004/03/16 14:16:05  graham
# Updates per comments from Bruce Lilly
#
# Revision 1.3  2004/02/19 11:49:40  graham
# Updated per Jacob Palme's comments
#
# Revision 1.2  2004/02/18 12:37:24  graham
# Reorganize permanent header definitions into three N3 files:
# Mail, Mime and specifications
#
# Revision 1.1  2004/02/18 11:38:09  graham
# Add separate MIME headers file to CVS
#
# Revision 1.5  2002/05/10 11:49:44  graham
# Cleaned up registry formatting
#
# Revision 1.4  2002/05/08 16:45:40  graham
# Bring header details into line with registry specification document
#
# Revision 1.3  2002/05/04 16:28:57  graham
# Initial header field registry data
#
# Revision 1.2  2002/05/03 16:02:42  graham
# Updated registry data, separated mail into permanent and provisional headers
#
# Revision 1.1.1.1  2002/05/02 22:32:33  graham
# no message
#