MEG0037 Use of V2 containers in V3
.02
06/06/2008
Purpose
Introduction
In the Version 3 Origination Deal concrete model there are places for Request and response elements.
The content of the request element is to contain data not held elsewhere in the model, but may be required for a particular request.
The content of the response element is the self contained response. It may be from any namespace, except the MISMO V2 null namespace.
1.1 Audience
Software developers working with MISMO specifications who are familiar with XML and the Interoperability Principles described in «add reference»
1.2 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.3 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 MISMO 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.
Rational for this MEG
The extensible nature of the V3 response container raised the question of placing V2 content in that extensible place. It was determined NOT to define how to accomplish this and further to require the MISMO workgroup NOT to use this approach and further to discourage it‘s use between trading partners.
Content
Guidelines
| Ref |
Guideline |
| 37.1 |
Transaction specifications defined by a MISMO workgroup SHALL NOT contain a V2 subset. |
| 37.2 |
The MISMO Architecture Committee SHALL NOT approve any transaction specification that contains a V2 subset. |
| 37.3 |
Transaction specifications SHALL NOT be developed or published in a way that technically prevents the inclusion of a V2 subset. |
| 37.3.1 |
MISMO strongly discourages developers and implementers from the practice of inclusion of V2 subsets witin V3. |
| 37.4 |
MISMO SHALL NOT provide guidance or technical advice to any trading partner who chooses to develop implementations that ignore this rule. |
Metadata
| Release History |
| Date |
Release |
Comments |
| 06/16/2007 |
.01 |
Initial Version |
| 06/06/2008 |
.02 |
Updated format and modified content |
| Changes Since Last Version |
| None |
| Contacts |
| Name |
Organization |
Contact Details |
| Greg Alvord |
Optimal Blue |
galvord@optimalblue.com |
| Metadata |
| Element |
Description |
| Title |
Use of V2 containers in V3 |
| Identifier |
MEG0037 |
| Category |
Foundation |
| Publisher |
MISMO |
| Contributor |
|
¤
| Rights |
Copyright of MISMO. All rights reserved. |
| Date Created |
6/16/2007 11:30:00 AM |
| Date Modified |
6/6/2008 5:15 PM |
References
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.