As a single archive rets2schema.zip (190,602 bytes)
A graphical representation of aspects of the RETS schema are presented as a series of PNG images. While you can browse the images online or grab them from RETS2 Diagrams (5,845,999 bytes), it is better to load the model into the hyperModel tool and browse it there.
A sample image is provided here. While this diagram can be easily viewed in a browser, the more complicated images are very large and cumbersome to manipulate.
A free modeling tool, based on the book "Modeling XML Applications with UML" ISBN 0-201-70915-5, was used to generate the images. This tool is built around the Eclipse platform and may provide a better experience at navigating the diagrams which are provided here in static form. Be forewarned, this tool may interfere with other Eclipse modeling tools within the same environment. The safest course, should you install the application, is to create a new installation using the larger, full application download if you are using other Eclipse modeling tools. The tool can be downloaded from www.xmlmodeling.com
To provide a list of the various elements and their containing schema, refer to the HTML Javadoc style documentation Javadoc style documentation. This has been generated from the schema and annotations and provides a different view of the information. This document has been updated with the current schema changes.
At the in-person RETS meeting held in Austin several comments were offered that have been incorporated into the schema. The Venetian Blind design pattern - reuseable global definitions - was endorsed by the community. This replaces the Russian Doll design pattern. Work has continued on this refactoring with work focused on the TMS payloads over the last month. A duplicate enumeration has been removed from Features.xsd. There was no consensus on strong pattern matching on elements so the example pattern match has been removed from the Phone.xsd Email complexType. Additonal work has been done on generating programming stubs. This has resulted in some name changes to make the element names unique. While this is not required in the definition of schema, at least one of the schema-to-code-stubs converters was throwing errors when there were element names that had identical base element names.
At the in-person RETS2 Schema meetings held in August and September, additional changes have been added to a change request system. The report is detailed in the document RETS2 Schema Change Request Report 2007-10-08.
Older reports are here:
2007-07-26
2007-07-09
The change report details remaining work from the meetings in Boston. Additional changes are expected when people review the Listings and Properties. Please review the Listings schema. There have been changes, (Listings with Properties now contained in Listings).
To provide examples of the documents created by the schema, an automated process takes the information in the appinfo field of the schema and applies it to automatically generated schema instances. Refer to the different xsd instances here: samples . Substantial additional work is needed to create reasonable instance documents. Of the instance samples, Members, Offices and Properties may be the most complete. Please feel free to provide additional example values to make this complete.
Some samples of what can be done with the schema have been created.
An example of extending a schema is provided here and an instance document from that schema is provided here
A trivial example of using common complexType definitions to create a new schema is provided here and an instance document from that schema is provided here
Excel style tab-delimited views of the schema are presented here
ContactMethods (Adopted, August 2007)
Person (Adopted, August 2007)
Participants (Adopted, August 2007)
Association Member Transmittals
Teams (Adopted, August 2007)
Members ((Adopted, August 2007)
