24.02.2015 Views

Specification - RETS

Specification - RETS

Specification - RETS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Object<br />

Optional<br />

Required<br />

Resource<br />

Resource Element<br />

Resource Key<br />

Server<br />

Request ID<br />

StandardName<br />

SystemName<br />

what different types of searches are available (tax, open house,<br />

etc.).<br />

For purposes of <strong>RETS</strong> and its GetObject transaction, a collection<br />

of octets treated as a unit and associated with a unique resource<br />

element.<br />

A field or feature described by this specification but not required<br />

for an endpoint to be considered compliant. The specification<br />

states the action to be taken by a compliant system in the absence<br />

of an optional field. The fact that the specification designates a<br />

field as optional does not mean that the recipient of a transaction<br />

that is missing optional fields is required to provide all services<br />

that could be required if the field were present.<br />

A compliant server or client MUST include any field designated<br />

as required. A transaction that does not include every required<br />

field MUST be rejected by the recipient.<br />

A collection of data having the external appearance of belonging<br />

to a single database and being accessible for search or update via<br />

<strong>RETS</strong> transactions.<br />

An individual record from a resource identified by a Resource<br />

Key.<br />

The unique key that identifies a resource element.<br />

The system providing data (also referred to as the “host”).<br />

A client-provided character string of up to 64 printable characters<br />

which uniquely identifies a request to a client. The contents are<br />

implementation-defined. Defined in Section 3.4, “Optional Client<br />

Request Header Fields”.<br />

The name of a data field as it is known in the Real Estate<br />

Transaction Standard Data Dictionary.<br />

The name of a data field as it is known in the metadata.<br />

Version 1.7.2 1-3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!