MEG0034 Embedded File Profile
Draft .02 11/15/2006 2:00 PM
Content
Structure
Overview
The Embedded File Container SHALL be defined as follows:
Metadata
Version .02
11/15/2006
| Release History |
| Date |
Release |
Comments |
| 11/10/2006 |
.01 |
Initial Version |
| 11/15/2006 |
.02 |
Update to content |
| Changes Since Last Version |
| See above |
| Known Issues |
| Additional Review Required |
| Contacts |
| Name |
Organization |
Contact Details |
| <ENTER NAME> |
MISMO |
<ENTER CONTACT DETAILS> |
| Metadata |
| Element |
Description |
| Title |
MEG0034 Embedded File Use Profile |
| Identifier |
MEG0034 |
| Subject |
Use of Embedded File in the MISMO Standard |
| Description |
Use of Embedded File in the MISMO Standard |
| Type |
|
| Source |
|
| Relation |
All MISMO Process Areas & Implementation |
| Coverage |
<ENTER COVERAGE HERE> |
| Creator |
<ENTER CREATOR HERE> |
| Publisher |
MISMO |
| Contributor |
Applies equally well to Version 2.x and 3.x |
| Rights |
Copyright of MISMO. All rights reserved. |
| Date Created |
11/10/2006 12:00:00 PM |
| Date Modifiend |
11/15/2006 02:00:00 PM |
| Format |
Text |
| Language |
En |
References
Purpose
1. Introduction
1.1 Context
There is often a business need to pass a print image or other non-XML file format within a defined MISMO standard. When this is the case, MISMO recommends the use of a generic Embedded File Element. The Embedded File Element allows for maximum flexibility to identify and carry a variety of file types.
1.2 Purpose
1.3 Scope
1.4 Audience
1.5 Terminology
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119. See «add reference to MISMO glossary for terminology used in this MEG».
1.6 Document Status
The information supplied in this document reflects the MISMO interoperability principles at the time of writing. It is a living document, which will be updated as required to reflect the evolving nature of XML technologies and service requirements identified by MISO constituency. Comments on this document should be sent to the MISMO designated contact identified in the document preface. MISMO does not accept any liability for the accuracy, adequacy or completeness of the information contained in these Guidelines.
2. Rationale for this MEG
Comments
None.
Disclaimer
Circulation Material in this guideline may be reproduced free of charge without requiring specific permission provided that the source is acknowledged, the document title given and the material is used in context.
Copyright All material in these MISMO Engineering Guidelines are the copyright of the MISMO. All rights are reserved.