OntologWiki: CCTRep Binary

CCTRepBinary (L3)

02-000 Binary Object. Type (L4)

A set of finite-length sequences of binary octets. Shall also be used for Data Types representing graphics (i.e., diagram, graph, mathematical curves or similar representations), pictures (i.e. visual representation of a person, object, or scene), sound, video, etc. (L5)

Binary Object (L6)

The following diagram shows one possible mapping between the Binary Object core component type and classes in the SUMO. (L7)

(L8)

OC: Binary Object (L9)

PT: Type (LA)

02-001 Binary Object. Content (LB)

A set of finite-length sequences of binary octets. (LC)

PDT: binary (LD)

02-002 Binary Object. Format. Text (LE)

[ScottLHolmes] This appears to be a reference to the Content Component Restrictions. I was unable to find anything more about this, except what appears to be a mistake made in an earlier version of the approved table. (LF)

02-003 Binary Object. Mime. Code (LG)

Mime.Code is the mime type of the binary object. Reference IETF RFC 2045, 2046, 2047 (LH)

The header Content-type indicates the type and subtype of the message content, for example: Content-type: text/plain (LI)

The combination of type and subtype is generally called a MIME type. A large number of file formats have registered MIME types. (LJ)

[ScottLHolmes] The terminology Mime. Code is not a common usage in the texts relating to the referenced RFCs. I'm assuming that this supplementary component is refering to the Content-type specificiation in a typical MIME header. (LK)

IETF RFC 204X - MIME (LL)

Example: (LM)

 Content-Type: text/plain;
 charset="iso-8859-1"
 Content-Transfer-Encoding: 7bit    (LN)

RFC: 2045 MIME Part 1 - Format of Internet Message Bodies This initial document specifies the various headers used to describe the structure of MIME messages. (LO)

RFC: 2046 MIME Part 2 - Media Types This second document defines the general structure of the MIME media typing system and defines an initial set of media types. (LP)

RFC: 2047 MIME Part 3 - Message Header Extensions for Non-ASCII Text The third document, RFC 2047, describes extensions to RFC 822 to allow non-US-ASCII text data in Internet mail header fields. (LQ)

IANA Registered MIME Types (LR)

UBL Unspecialized Data Types UBL seems to call Binary Object. Mime. Code "Mime Type" as part of the Unspecialized Data Types specification. (LS)

MIME Type - ContentType (LT)

Type (LU)

Sub Type (LV)

02-004 Binary Object. Mime. Character Set. Code (LW)

Any text type has an additional charset parameter that can be included to indicate the character encoding. (LX)

[ScottLHolmes] The terminology Mime. Character Set. Code is not a common usage in the texts relating to the referenced RFCs. I'm assuming that this supplementary component is refering to the Content-type specificiation in a typical MIME header. (LY)

IANA Official names for character sets The character set most commonly use in the Internet and used especially in protocol standards is US-ASCII, this is strongly encouraged. The use of the name US-ASCII is also encouraged. (LZ)

UBL Character Set Code The character set of the binary object if the mime type is text. (M0)

02-005 Binary Object. Mime. Encoding. Code (M1)

Content-Transfer-Encoding MIME (RFC 2045) defines a set of methods for representing binary data in ASCII text format. The content-transfer-encoding: MIME header indicates the method that has been used. Typically encountered values for this header include: (M2)

7bit - up to 998 octets per line of the code range [1..127]\{CR, NL}. This is the default value. (M3)
8bit - up to 998 octets per line of the code range [1..255]\{CR, NL}. This can be used only if both the sending and receiving mail transfer agents support the 8bit MIME transport SMTP extension. (M4)
binary - any sequence of octets (M5)
quoted-printable - used for text data consisting primarily of US-ASCII characters (M6)
base64 - used for arbitrary binary data (M7)

Example: Content Transfer Encoding (M8)

 Content-transfer-encoding: base64    (M9)

CCTRepBinary