MISMO® Engineering Guide
MEG00XX TITLE
Version: (X.XX)
Last Updated: (MM/DD/YYYY)
Status: (draft/approved)
P1. Purpose
P1.1 Introduction
<developer provided content: introduction, scope, content, etc>
P1.2 Audience
This MEG was written for the following groups:
- MISMO Workgroup members developing MISMO messages.
- Designers and users of systems that create and consume the XML instance documents used in Real Estate Finance transactions.
- Technical or business professionals wishing to evaluate MISMO specifications.
P1.3 Terminology
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
- MUST - This word, with the term “REQUIRED”, indicates an absolute requirement of the specification.
- MUST NOT - This phrase indicates an absolute prohibition of the specification.
- SHOULD - This word, or the adjective “RECOMMENDED”, means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
- SHOULD NOT - This phrase, or the phrase “NOT RECOMMENDED” means that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.
- MAY - This word, or the adjective “OPTIONAL”, indicates that the specification allows the designer to choose whether or not to comply.
P1.4 Assumptions
The information supplied in this document reflects the MISMO architecture development and 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 the MISMO constituency.
P1.5 Rationale
<developer provided content: high level statement on the core purpose of this MEG.>
C1. Content
C1.1 Guidelines
| Ref |
Guideline |
| MEGNumber.1 |
Guideline Content for number 1 |
| MEGNumber.2 |
Guideline Content for number 2 |
| Element |
Description |
| Title |
|
| Identifier |
MEG00xx |
| Category |
|
| Date Created |
09/23/2006 11:15:00 AM |
| Last Updated |
12/17/2008 06:20:00 PM |
| Publisher |
MISMO |
| Copyright |
©2008 MISMO. All Rights Reserved. |
M1.1 Release History
| Release Date |
Version No. |
Comments |
| DATE |
X.XX |
<developer provided content> |
M1.2 Known Issues or Omissions
None. <developer provided content>
| Name |
Organization |
Contact Details |
| MISMO Staff |
MISMO |
info@mismo.org |
M1.4 References
Comments
T1. Terms and Conditions
T1.1 Disclaimer
MISMO accepts no liability for the accuracy, adequacy, or completeness of the information contained in this MISMO Engineering Guideline (MEG).
T1.2 Reproduction
Material in this MEG may be reproduced free of charge without obtaining explicit permission from MISMO, provided that the source is acknowledged, the document title given, and the material is used in context.
T1.3 Copyright
©2008 MISMO. All material in this MEG is the property of MISMO. All Rights Reserved.