|
|
|
MEG0007 Class Words
Version: 1.2
Last Updated: 03/30/2009
Status: Submitted to RAWG
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 data point names (terms). It is helpful to human readers of both schema and messages if the names of data points indicate the type of information they carry. For this reason, the MISMO Architecture and Core Data / Structures Workgroups have established a list of approved Class Words that must make up the last component of all MISMO data point terms.
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.
To provide feedback on this MEG, go to the Comments tab and click on New Entry.
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.
P1.5 Rationale
MISMO WGs developing schema will need to create data points if a given data requirement cannot be met by a term in the Logical Data Dictionary. In order to limit the number of data points and ensure consistency of similar data, all data point names must end with a Class Word. This MEG provides a single point of reference for MISMO Class Words, including definitions, required format, and example usage.
Content
C1. Content
C1.1 Guidelines
| Ref |
Guideline |
| 7.1 |
Every data point name (term) MUST end in one of the following Approved Class Words:
Amount
Code
Count
Date
Datetime
Day
Description
Identifier
Indicator
Month
Name
Number
Percent
Rate
Resource
Text
Time
Type
URI
Value
XML
XPATH
Year |
| 7.2 |
A given Class Word SHOULD be used for terms meeting the Class Word’s associated definition as specified in 7.6. |
| 7.3 |
Each Class Word MUST take the associated data type as specified in 7.6. Data elements MUST take the MISMO and XML Data Types of their component Class Words. |
| 7.4 |
Each of the MISMO Data Types has a corresponding “Sensitive” Data Type to identify data points classified as non-public personal information. For example, MISMOString can also be implemented as MISMOStringSensitive. See MEG0012 for more information. |
| 7.5 |
Data elements MUST follow the format of their component Class Words. |
| 7.6 |
Approved Class Words have the Definitions, MISMO and XML Data Types, and Formats specified below. Examples are provided to illustrate proper (or improper) use. |
| 7.6.1 |
Amount: The numeric value of a quantity of monetary currency in US dollars unless otherwise specified.
MISMO Data Type: MISMOAmount or MISMOInternationalAmount
XML Data Type: complexType having xsd:decimal restriction with CurrencyURI attribute (optional for MISMOAmount). CurrencyURI is based on ISO 4217 Standard and is ALWAYS assumed to be US Dollars unless otherwise specified.
Format:
1. Values MUST NOT contain any punctuation other than a decimal point and sign value.
2. The decimal point MUST be the U.S. nationalization character “.” in the designated character encoding. UTF-8 is assumed when not specified.
3. Whole dollar amounts MAY be represented either with or without a decimal. The number of decimal places allowed is not limited.
4. There MAY be an optional CurrencyURI attribute.
Examples:
1. Given that Base Loan Amount is “BaseLoanAmount” and the amount is “$225,000”, one correct usage is:
<BaseLoanAmount>225000</BaseLoanAmount>
2. Given BaseLoanAmount equal to “$225,000”, one correct usage is:
<BaseLoanAmountCurrencyURI=“urn:org:iso:standards:4217:USD”
>225000.00<
/BaseLoanAmount>
3. Given that Asset Cash Or Market Value Amount is “AssetCashOrMarketValueAmount” and the price is “150,000.23 Swiss Francs”:
<AssetCashOrMarketValueAmount CurrencyURI=“urn:org:iso:standards:4217:CHF”
>150000.23<
/AssetCashOrMarketValueAmount>
|
| 7.6.2 |
Code: A character string of one or more letters or numbers that for the purpose of brevity represents a definitive value. The Code and the entity it represents usually are maintained in a common dictionary by an authoritative source. The Code might not bear any resemblance to the represented entity. Used in the names of data elements whose allowable values can be represented as enumerated lists.
MISMO Data Type: MISMOIdentifier
XML Data Type: complexType having xsd:string restriction with CodeOwnerURI and CodeEffectiveDate attributes (optional)
Format:
SHOULD be used in conjunction with a URI identifying the organization that maintains the code list or dictionary.
Examples:
Given that the USPS State Code for Texas = “TX”:
<USPSStateCode ownerURI= “urn:gov:USPS:USPSStateCode”>TX</USPSStateCode>
Examples of other codes include:
1. FIPS State Code (Texas = “48”)
2. FIPS County Code (Pima County = “04019”)
3. Credit Comment Code (Insufficient Data = “23”)
|
| 7.6.3 |
Count: The numeric value of a quantity of non-monetary items of the same kind. Used to keep track of how many of a particular kind of item exists.
MISMO Data Type: MISMOCount
XML Data Type: xsd:integer xsd:decimal (union)
Examples:
1. Given that the number of bedrooms in a dwelling is “BedroomCount” and there are four bedrooms:
<BedroomCount>4</BedroomCount>
2. Given that the base flood elevation of a property expressed in feet is “BaseFloodElevationFeetCount” and the total feet is “2,350”:
<BaseElevationFeetCount>2350</BaseElevationFeetCount>
|
| 7.6.4 |
Date: Numeric value representing a specific day of the Gregorian Calendar made up of a combination of day, month, and year.
MISMO Data Type: MISMODate
XML Data Type: xsd:gYear xsd:gYearMonth xsd:date (union) with SensitiveIndicator attribute (optional)
Format:
1. Full dates MUST be represented in the extended format YYYY-MM-DD where:
YYYY is a four-digit year, “0000” through “9999”
MM is a two-digit month of that year, “01” through “12”
DD is a two-digit day of that month, “01” through “31”
- is the required separator between YYYY-MM-DD
Padded zeros must be used.
2. The forms of Date supported are a subset of the ISO 8601 date microformat that uses the XML schema base data type:
Supported
2009
2009-01
2009-01-15
20090115
(DATE)Z Date at Universal Time Coordinate
(DATE)-hh:mm Date at specified time zone
NOT Supported
2006-042 Day 42 of 2009
2009-W05-4 Thursday (Day 4), Week 5, 2009
23:59:59 One second to midnight (See Datetime and Time Class Words)
23:59 One minute to midnight (See Datetime and Time Class Words)
(DATE)T(TIME) (See Datetime and Time Class Words)
(DATE)T(TIME)Z Datetime at Universal Time Coordinate
(DATE)T(TIME)-hh:mm Datetime at specified time zone
(TIME)Z Time at Universal Time Coordinate
(TIME)-hh:mm Time at specified time zone
Examples:
Given the date a borrower signed a loan application is “BorrowerApplicationSignedDate” and this event occurred on “March 12, 2008”, the date could be represented in the following ways:
1. In the usual 10-character format:
<BorrowerApplicationSignedDate>2008-03-12< /BorrowerApplicationSignedDate>
2. If only “March 2008” is provided:
<BorrowerApplicationSignedDate>2008-03</BorrowerApplicationSignedDate>
3. If signed in Baghdad, Iraq:
<BorrowerApplicationSignedDate>2008-03-12+03:00</BorrowerApplicationSignedDate>
|
| 7.6.5 |
Datetime: MUST NOT be used unless both the date and time are required fields. If one or the other is optional, date and time MUST be specified as separate Date and Time elements.
MISMO Data Type: MISMODatetime
XML Data Type: xsd:Datetime with SensitiveIndicator attribute (optional)
Format:
Combines Date and Time Class Word formats with the time designator “T” separating Date and Time. Any proper representation of date and time described in this MEG may be used. White space is not permitted.
YYYY-MM-DDThh:mm:ss
2. With the time zone indicator “Z”:
YYYY-MM-DDThh:mm:ss Z
3. With a time zone offset:
YYYY-MM-DDThh:mm:ss-hh:mm
The forms of Datetime supported are a subset of the ISO 8601 Datetime microformat that uses the XML schema base data type.
Supported
2009
2009-01
2009-01-15
20090115
23:59:59 One second to midnight
(DATE)T(TIME)
(DATE)Z Date at Universal Time Coordinate
(DATE)-hh:mm Date at specified time zone
(DATE)T(TIME)Z Datetime at Universal Time Coordinate
(DATE)T(TIME)-hh:mm Datetime at specified time zone
(TIME)Z Time at Universal Time Coordinate
(TIME)-hh:mm time at specified time zone
NOT Supported
2009-042 Day 42 of 2009
2009-W05-4 Thursday (Day 4), Week 5, 2009
23:59 One minute to midnight
Examples:
1. Given that the exact date and time on which a party issues a price quote for a loan is “LoanPriceQuoteDatetime” and this event occurred on “December 30, 2008” at “10:13:59”:
<LoanPriceQuoteDatetime>2008-12-30T10:13:59:15</LoanPriceQuoteDatetime>
2. Given the date a borrower signed a loan application is “BorrowerApplicationSignedDate” and this event occurred on “March 12, 2008” at “2:00 pm” in the “Mountain Time Zone”:
<BorrowerApplicationSignedDate>2008-03-12T14:00:00-07:00</BorrowerApplicationSignedDate>
|
| 7.6.6 |
Day: Numeric value representing the day segment of the Gregorian calendar date.
MISMO Data Type: MISMODay
XML Data Type: xsd:gDay
Format:
A day is represented in the format:
DD
Where DD is a two-digit day of the month, “01” through “31”.
Padded zeros must be used along with the W3C required “- - -” which proceeds the value.
Examples:
Given that the day of each month that principal and interest must be remitted to an investor is “InvestorRemittanceDay” and this day is the “14th”:
<InvestorRemittanceDay>- - -14</InvestorRemittanceDay>
|
| 7.6.7 |
Description: A word, phrase or more lengthy statement that is used to describe something. Its purpose may be to interpret or make something more understandable to the reader. It may describe a specific person, place, or thing but does not necessarily identify the entity uniquely.
MISMO Data Type: MISMOString
XML Data Type: xsd:string
Format:
No formatting restrictions exist for this class word.
Examples:
Given that information about the Federal, state, or local agency program under which a loan is originated is “AgencyProgramDescription”:
<AgencyProgramDescription>FHA 203(k) Loan Program</Agency Program Description>
|
| 7.6.8 |
Identifier: Alphanumeric string used to establish the identity of and uniquely distinguish one instance of an object from other similar items in a collection. The identifier may conform to some formal identification system. In common business usage Identifiers often are called “Numbers.”
MISMO Data Type: MISMOIdentifier
XML Data Type: complexType having xsd:string restriction with IdentifierOwnerURI and IdentifierEffectiveDate attributes (optional)
Format:
No formatting restrictions exist for this class word.
Examples:
Examples of identifier values for individuals include Driver’s License Number and Appraiser’s License Number. Examples of identifier values for objects include Parcel Number, Account Number, etc. Given that a Driver’s License Number is “DriversLicenseIdentifier” and the number is “VA1236899484”:
<DriversLicenseIdentifier IdentifierOwnerURI=“http://www.virginia.gov” IdentifierEffectiveDate=“2008-02-09”>VA1236899484</DriversLicenseIdentifier>
|
| 7.6.9 |
Indicator: Identifies a boolean condition with two mutually exclusive values such as “yes/no”, “true/false” or “1/0”. A precise definition of the meaning of the true value should be given.
MISMO Data Type: MISMOIndicator
XML Data Type: xsd:Boolean
Format:
“True”/“False” or “1”/“0” are valid. For canonicalization, “True”/“False” should be used
Examples:
Given that an “AssumabilityIndicator” is used to specify that a loan is either assumable (True) or not assumable (False):
<AssumabilityIndicator>True</AssumabilityIndicator>
<AssumabilityIndicator>False</AssumabilityIndicator>
NOTE: If a data element may take another value (e.g., “Unknown” or “Not Applicable”), then Type should be used instead of Indicator, and the meanings of all possible values should be clearly defined.
|
| 7.6.10 |
Month: Numeric value representing the month segment of the Gregorian calendar date.
MISMO Data Type: MISMOMonth
XML Data Type: xsd:gMonth
Format:
The value MUST be represented as two digits along with the W3C required “- -” preceding the numeric values:
MM
Examples:
Given that the month of each year that disbursements from an escrow account are made to payees is “EscrowAccountDisbursementMonth” and this month is “March”:
<EscrowAccountDisbursementMonth>- -03</EscrowAccountDisbursementMonth>
|
| 7.6.11 |
Name: A textual label used as the common identifier of a person, place or thing. A Name is usually meaningful in some language and is the primary means of identification of objects for humans.
MISMO Data Type: MISMOString
XML Data Type: xsd:string
Format:
No formatting restrictions exist for this class word.
Examples:
1. Given that that the name of a product that is available from an specific AVM Software package is “AVMSoftwareProductName” and the product’s name is “PriceDelux”:
<AVMSoftwareProductName>PriceDelux</AVMSoftwareProductName>
2. Given that the first name of a borrower is “BorrowerFirstName” and the borrower’s first name is “Greg”:
<BorrowerFirstName>Greg</BorrowerFirstName>
3. Given that the name of a company is “CompanyName” and the company’s name is “Big Brothers”:
<CompanyName>BigBrothers</CompanyName>
NOTE: Unlike an Identifier, a name is not necessarily unique.
|
| 7.6.12 |
Number: Used to represent a specific numerical value. Frequently used for the purpose of identification.
MISMO Data Type: MISMONumeric
XML Data Type: xsd:integer xsd:decimal (union)
Format:
No formatting restrictions exist for this class word.
Examples:
Given that the number of payment adjustment periods is “PaymentAdjustmentPeriodNumber” and payments may be adjusted “three” times:
<PaymentAdjustmentPeriodNumber>3</PaymentAdjustmentPeriodNumber>
|
| 7.6.13 |
Percent: A Percent is the numeric ratio of two numbers, multiplied by 100.
MISMO Data Type: MISMOPercent
XML Data Type: xsd:decimal
Format:
1. Values MAY be represented with a decimal point.
2. Values MUST NOT contain any punctuation other than a decimal point and sign value.
3. The decimal point MUST be the U.S. nationalization character “.” in the designated character encoding. UTF-8 is assumed when not specified.
Examples:
To express the Tax Rate of “0.055” as a Tax Percent, multiply the Tax Rate by 100 (0.055 x 100 = 5.5 or 5.5%):
<TaxPercent>5.5</TaxPercent>
|
| 7.6.14 |
Rate: Typically a ratio, a quantity measured with respect to another measured quantity, amount, charge, cost, or value. It is a numeric comparison between two values, a fraction that is expressed as a decimal.
MISMO Data Type: MISMORate
XML Data Type: xsd:decimal
Format:
1. Values MAY be represented with a decimal point.
2. Values MUST NOT contain any punctuation other than a decimal point and sign value.
3. The decimal point MUST be the U.S. nationalization character “.” in the designated character encoding. UTF-8 is assumed when not specified.
Examples:
Given that the state sales tax is “StateSalesTaxRate” and the tax rate is “5.5” percent:
<StateSalesTaxRate>0.055</StateSalesTaxRate>
|
| 7.6.15 |
Resource: |
| 7.6.16 |
Text: A string of unformatted alphanumeric characters which may be in the form of words.
MISMO Data Type: MISMOString
XML Data Type: xsd:string
Format:
No formatting restrictions exist for this class word.
Examples:
|
| 7.6.17 |
Time: An alphanumeric value specifying an instant of time that occurs in a specific pattern but not on a specific day, for example 12:00 pm (noon) every day, or 8:00 am every work day.
MISMO Data Type: MISMOTime
XML Data Type: xsd:time
Format:
MISMO’s time notation is based on ISO 8601. ISO 8601 uses a 24-hour clock. Time is assumed to be in UTC (Coordinated Universal Time roughly equal to Greenwich Mean Time).
1. Times MUST be represented in the extended format:
hh:mm:ss
hh is an hour between “00” and “24”, where “00” represents midnight at the start of a calendar day.
mm is a minute from “00” to “59”
ss is a second from “00” to “59”.
Padded zeros must be used.
“:” is the required separator between hh:mm:ss
2. If no value is provided for the “seconds” segment of a time, use:
hh:mm
3.Time MAY have the time zone designator “Z” for a time zone offset. “Z” used alone means there is no time zone offset:
hh:mm:ssZ
4. Other time zones are specified by the offset from UTC in the format:
hh:mm:ss±hh:mm
The maximum value of a time zone offset is “±12:00”.
The forms of Time supported are a the subset of the ISO 8601 date mircoformat that uses the XML schema base data type.
1. 2009 NOT Supported
2. 2009-01 NOT Supported
3. 2009-01-15 NOT Supported
4. 20090115 NOT Supported
5. 2006-042 Day 42 of 2009 NOT Supported
6. 2009-W05-4 Thursday (day 4), Week 5, 2006 NOT Supported
7. 23:59:59 One second to midnight Supported
8. 23:59 One Minute to midnight NOT Supported
9. (DATE)T(TIME) NOT Supported
10. (DATE)Z Date at Universal Time Coordinate NOT Supported
11. (DATE)-hh:mm Date at specified time zone NOT Supported
12. (DATE)T(TIME)Z Datetime at Universal Time Coordinate NOT Supported
13. (DATE)T(TIME)-hh:mm Datetime at specified time zone NOT Supported
14. (TIME)Z Time at Universal Time Coordinate Supported
15. (TIME)-hh:mm time at specified time zone Supported
Examples:
1. Given that an investor’s daily cutoff time each business day for funding loans is “FundingCuttoffTime” and that time is “4:00 p.m”:
<FundingCutoffTime>16:00:00</FundingCuttoffTime>
where “16:00:00” = “4:00 p.m.” on the 24-hour clock.
2. When using UTC, if the time being described is one hour ahead of UTC, the zone designator would be “+01:00”, “+0100”, or simply “+01”. This is appended to the time in the same way that “Z” is above.
3. Convert between time zones using the following formula:
Time in zone B = Time in zone A − UTC offset for zone A + UTC offset for zone B
The time zone offset values within the US are:
Hawaii: “-10:00”
Alaska: “09:00”
Pacific: “-08:00”
Mountain Time: “-07:00”
Central Time: “06:00”
Eastern Time: “-05:00”
Atlantic Time: “-04:00”
Note that the zone designator needs to be adjusted appropriately for Daylight Savings Time.
4. Given a time of “6:30 p.m.”, any of the following expressions could be used:
18:30:00Z where “18:30:00” = “6:30 p.m.” on the 24-hour clock, and “Z” used alone means there is no time zone offset.
22:30:00+04 where the time = 22:30 - 4, which = 18:30 = 6:30 p.m.
15:00:00−03:30 where the time = 15:00 -(-3:30) which = 18:30 = 6:30 p.m.
|
| 7.6.18 |
Type: SHOULD be used for a term that has a specific enumerated list of allowable values. Only values specified on that list MAY be used in an instance of a message.
MISMO Data Type: N/A-Enumeration
XML Data Type: N/A-Enumeration
Format:
Message instance values MUST come from the associated enumerated list.
Examples:
Given the term ContactPointType with an enumerated list of allowable values: “Email”, “Fax”, “Other”, and “Phone”:
<ContactPointType>Email</ContactPointType> is a valid value.
<ContactPointType>address</ContactPointType> is not a valid value.
NOTE, if “Other” is selected, the element “ContactPointTypeOtherDescription” will hold the intended value.
|
| 7.6.19 |
URI: Represents a Uniform Resource Identifier Reference (URI). An anyURI value can be absolute or relative, and may have an optional fragment identifier (i.e., it may be a URI Reference). This type should be used to specify the intention that the value fulfills the role of a URI as defined by RFC 2396 , as amended by RFC 2732 .
MISMO Data Type: N/A
XML Data Type: xsd:anyURI
Lexical representation
The ·lexical space· of anyURI is finite-length character sequences which, when the algorithm defined in Section 5.4 of XML Linking Language is applied to them, result in strings which are legal URIs according to RFC 2396 , as amended by RFC 2732 .
Note: Spaces are, in principle, allowed in the ·lexical space· of anyURI, however, their use is highly discouraged (unless they are encoded by %20).
Format:
Values MAY use either the URN (Universal Resource Name) or the URL (Universal Resource Location) form of a URI
Examples:
1.Acme Mortgage quotes a price to Alice, a broker at Bob‘s brokerage.
<LoanPriceQuoteIdentifier IdentifierOwnerURI=“urn:com:AcmeMortgage:LoanPriceQuoteIdentifier:7254”>102.375<LoanPriceQuoteIdentifier> |
| 7.6.20 |
Value The specific content of any data type for the concept to which it is bound. MISMO Value is a generalization of any simple type.
MISMO Data Type: MISMOString
XML Data Type: xsd:string
Format:
Values MAY be represented as any string:
Green.
Examples:
1. If “MILoanLevelCreditScoreValue” is “801”:
<MILoanLevelCreditScoreValue>801</MILoanLevelCreditScoreValue>
2. Given that “AutomatedUnderwritingSystemResultValue” is “Refer”:
<AutomatedUnderwritingSystemResultValue>Refer</AutomatedUnderwritingSystemResultValue>
|
| 7.6.21 |
XML An element that contains mixed content of CDATA or elements from any namspace used to hold concept(s) and value(s) with meaning or interpretation defined outside of MISMO. The content MUST be valid XML. This data type is used exclusively for holding the content in the EmbeddedContent term used by the FILE_RESOURCE type.
MISMO Data Type: MISMOXML
XML Data Type: xsd:anyType
Format:
The content MUST use the encoding of the root document; the content MUST NOT contain an XML declaration:
Plain text.
Examples:
1. If “EncodingType” is “None” and “MIMETypeIdentifier” is “text/html”:
<EmbeddedContentXML><html xmlns=“http://www.w3.org/1999/xhtml”>
<head><title>HW</title></head>
<body><p>Hello World</p></body>
</html></EmbeddedContentXML>
2. If “EncodingType” is “Base64” and “MIMETypeIdentifier” is “text/html”:
<EmbeddedContentXML>PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCjwhRE9DVFlQRSBodG1s
IFBVQkxJQyAiLS8vVzNDLy9EVEQgWEhUTUwgMS4wIFN0cmljdC8vRU4iICJodHRwOi8vd3d3
LnczLm9yZy9UUi94aHRtbDEvRFREL3hodG1sMS1zdHJpY3QuZHRkIj4NCjxodG1sIHhtbG5z
PSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hodG1sIj48aGVhZD48dGl0bGU+SFc8L3RpdGxl
PjwvaGVhZD48Ym9keT48cD5IZWxsbyBXb3JsZDwvcD48L2JvZHk+PC9odG1sPg==</EmbeddedContentXML>
|
| 7.6.22 |
XPath |
| 7.6.23 |
Year: Numeric value representing the year segment of the Gregorian calendar date.
MISMO Data Type: MISMOYear
XML Data Type: xsd:gYear
Format:
Values MUST be represented as four digits:
YYYY
where “YYYY” is a four-digit year “0000” through “9999”.
Examples:
1. Given that the year in which an individual acquired a property is “PropertyAcquiredYear” and that year was “1998”:
<PropertyAcquiredYear>1998</PropertyAcquiredYear>
2. Given that the model year of an automobile is “AutomobileModelYear” and that year is “2008”:
<AutomobileModelYear>2008</AutomobileModelYear> |
Metadata
| Element |
Description |
| Title |
Class Words |
| Identifier |
MEG0007 |
| Category |
Convention |
| Date Created |
8/6/2006 6:51:00 PM |
| Last Modified |
12/19/2008 12:08:00 AM |
| Publisher |
MISMO |
| Copyright |
©2008 MISMO. All Rights Reserved. |
M1.1 Release History
| Release Date |
Version No. |
Comments |
| 9/25/2006 |
0.01 |
Initial Version |
| 04/08/2008 |
0.02 |
Update MEG format |
| 04/18/2008 |
0.03 |
Changes per 4/17 D3 meeting |
| 06/06/2008 |
0.04 |
Changes per 5/15 D3 meeting (term vs. data points) |
| 09/03/2008 |
0.05 |
Deleted certain class words and reformatted. |
| 11/22/2008 |
0.06 |
Deleted and added class words, revised definitions, data types, reformatted. |
| 11/25/2008 |
0.07 |
Modfications based on open questions from .07 update. |
| 11/27/2008 |
0.08 |
Added clairification of ISO 8601 formats supproted for Date, Time and Datetime. Where there were questions of restirctions about class words with no reatriction stated it explictly. |
| 12/03/2008 |
0.09 |
Updated MISMOAmount to include CurrencyURI attribute. |
| 12/04/2008 |
0.10 |
Made changes to MISMOAmount, MISMOIndicator, MISMODay and MISMOMonth based on 12/4 D3 call. |
| 12/09/2008 |
1.0 |
Approved by MISMO Residential Governance Committee |
| 12/19/2008 |
1.1 |
Global modifications to MEG format; changed “Disclaimer” tab to “Terms” and updated contents. |
M1.2 Known Issues or Omissions None
| Name |
Organization |
Contact Details |
| MISMO Staff |
MISMO |
info@mismo.org |
M1.4 References
| Title |
Location |
| RFC 2119 |
http://rfc.net/rfc2119.html |
| ISO 4217 |
http://www.iso.org/iso/support/faqs/faqs_widely_used_standards/
widely_used_standards_other/currency_codes/currency_codes_list-1.htm |
Comments
None.
Terms
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 used in context.
T1.3 Copyright ©2008 MISMO. All material in this MEG is the property of MISMO. All Rights Reserved.
|
Last modified at 8/13/2010 8:15 AM by PROD-SPOINT\administrator
|
|
|
|