Structure
| CDT | Attributes | Category | Object Class Term | Property Term | Representation Term | Type || Type Name | Length | Cardinality | Remarks | |
|---|---|---|---|---|---|---|---|---|---|---|
| Picture | complexType | Picture | Type | XSD | base64Binary | |||||
| mimeCode | Attribute | Picture | MIME | Code | GDT | MIMECode | 0..1 | |||
| characterSetCode | Attribute | Picture | Character Set | Code | GDT | CharacterSetCode | 0..1 | |||
| format | Attribute | Picture | Format | Text | XSD | token | 0..1 | |||
| fileName | Attribute | Picture | File | Name | XSD | string | 0..1 | |||
| uri | Attribute | Picture | Uniform Resource | Identifier | XSD | anyURI | 1..1 |
Detailed Description and Value Ranges
The element value of Picture is based on the XML-scheme-specific built-in data type xsd:base64binary. This enables any binary data to be represented using base64 encoding. This is done using the base64 Content-Transfer-Encoding procedure (see IETF RFC 2045).
The following MIME types are available for mimeCode (see IANA Media Types of Internet Assigned Numbers Authority (IANA), Status: November 2002). The particular format of the media type is specified by the subtype, which follows the slash, see: MIME Types.
The following character sets are available for "charsetCode":
| MIME Type | Description | Reference |
|---|---|---|
| iso-8859-n | n is a placeholder for the number of the relevant ISO character set from 1 to 9 (for example, iso-8859-1) | IETF RFC 2045 IETF RFC 2046 |
| us-ascii | IETF RFC 2046 IETF RFC 2046 |
The following URI schemes are available for the scheme-specific part in the URI (see Uniform Resource Identifer (URI) Schemes, Internet Assigned Numbers Authority (IANA)):
| Scheme Name | Description | Reference |
|---|---|---|
| cid | content identifier | IETF RFC 2392 |
| uuid | Universal Unique Identifier Scheme | UUID |
Detailed Description of Attributes and Elements
| Attribute/Element | Description |
|---|---|
| mimeCode | Identifies the medium type (image, audio, video, application) of the binary content according to the MIME type definition in IETF RFC 2046 and the corresponding MIME type recommendations. |
| characterSetCode | Identifies the specific character set of text data. |
| format | Describes the format of the binary content if the format is not clear or unique from the "mimeCode". |
| fileName | Contains the corresponding name or file name of the binary content according to the MIME protocol IETF RFC 1341. |
| uri | References the physical location of "Sound" if this is reavailableed as a MIME attachment in a SOAP message or in an ebXML-MSG message. The syntax of the URI is defined in the IETF RFC 2396 recommendation and is as follows: <scheme>.< schemespecific part> |
Facets of Content Component
| Facet | Description | Example |
|---|---|---|
| pattern | Pattern is a constraint of the content component. The representation of pattern must be based on regular expression defined by W3C XML Schema (Part II). | [3-5][0-9] {3}.[0-9]{2} |
| whiteSpace | whiteSpace is a constraint of special characters in the content component. whiteSpace must be one of the following values:
|
whiteSpace value="preserve|replace|collapse" |
Integrity Conditions
Not specified.
Use
Picture can be used for binary data of pictures, photos, arts, clip arts which are reavailableed in a binary notation.
Notes
The useful data in Picture can be delivered either as an element value using base64 octet representation or as a MIME attachment. "Picture" cannot be used to reference a file that is located on a Web server. The global data type "WebAddress" is available for this purpose.
If Picture is in a MIME attachment, the URI must reference the corresponding "Content ID" of the respective MIME attachment. The following URI schemes are used for this purpose:
- cid - Identifies a freely defined "Content ID" (see ebMS V2.0).
- uuid - Identifies a unique identification in accordance with the UUID guidelines (see WS Attachment).
It is not necessary to specify the "typeCode" and "fileName" attributes in a MIME attachment, since this information is contained in the MIME attachment itself.