Architecture Workgroup

Purpose - Guidelines for Creating Messages

1. Introduction

The MISMO Reference Model is a schema-based representation of the pieces necessary to communicate a variety of messages, or execute transaction, for the real estate finance industry. As such, the reference model is extremely large and robust. Therefore each MISMO Workgroup has the opportunity to limit the scope of their individual messages and use only the pieces of the reference model deemed necessary.

P1.1 Audience

This MEG was written for the following groups:

1. MISMO Workgroup members developing MISMO messages.
2. Designers and users of systems that create and consume the XML instance documents used in Real Estate Finance transactions.
3. Technical or business professionals wishing to evaluate MISMO specifications.

P1.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.

1. MUST - This word,or the terms “REQUIRED” or “SHALL”, mean that the definition is an absolute requirement of the specification.

2. MUST NOT - This phrase, or the phrase “SHALL NOT”, mean that the definition is an absolute prohibition of the specification.

3. SHOULD - This word, or the adjective “RECOMMENDED”, mean 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.

4. SHOULD NOT - This phrase, or the phrase “NOT RECOMMENDED” mean 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.

5. MAY - This word, or the adjective “OPTIONAL”, mean that an item is truly optional.

P1.3 Document Status

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.

P2. Rationale for rescinding this MEG

MEG0026 was originally conceived to provide guidelines for workgroups to develop individual messages from the Version 3.x Reference Models. Since the decision has been made that workgroups will not publish individual schemas for their transactions; instead publishing Implementation Guides and sample XML messages for their specific business case use of a subset of the model.

Content

Guidelines