MEG0004 Schema Language Recommendations
Version: 0.02
Last Updated: 11/27/2008
Status: Draft
Purpose
P1. Purpose
P1.1 Introduction
The MISMO messages supporting Real Estate Finance transactions are produced, processed, and exchanged by systems. A key design objective for the schema on which these messages (XML instances) are based is that they be precise enough to be used for message validation. Since schema files are the primary documentation for designers and users of systems that process MISMO messages, the schema also should enable human readers to understand the structure and character of the instance they describe. Schema files should describe the XML instance accurately and clearly. One way to achieve this clarity is to be consistent in the naming and structure of the container that hold data points(terms). It is helpful to human readers of both schema and messages if the names of containers.
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
. See «add reference to MISMO glossary for terminology used in this MEG».
P1.4 Assumptions
This document reflects the MISMO Architecture Development principles at the time of writing. It is a living document that is updated as required to reflect the evolving nature of XML technologies and requirements identified by the MISMO constituency. For document change management information, go to the Metadata tab. To provide feedback on this MEG, go to the Comments tab and click on New Entry.
P1.5 Rationale
MISMO WGs developing schema will need to create containers that hold data points if a given coantiner requirement cannot be met by a container term in the Logical Data Dictionary. This MEG provides a single point of reference for the use of XSD Schema for MISMO.
Content
None.
Metadata
| Element |
Description |
| Title |
MISMO Business Terminology |
| Identifier |
MEG0001 |
| Category |
Foundation |
| 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
| Date |
Release |
Comments |
| 11/25/2008 |
0.01 |
Initial Version |
| 12/17/2008 |
0.02 |
Global MEG formatting changes; Changed “Disclaimer” tab to “Terms” and updated content. |
M1.2 Known Issues or Omissions
None.
| Name |
Organization |
Contact Details |
| MISMO Staff |
MISMO |
info@mismo.org |
M1.4 References
Comments
None.
Terms
T1. Terms and Conditions
1.1 Disclaimer
MISMO accepts no liability for the accuracy, adequacy, or completeness of the information contained in this MISMO Engineering Guideline (MEG).
1.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 used in context.
1.33 Copyright
©2008 MISMO. All material in this MEG is the property of MISMO. All Rights Reserved.