Specification - RETS

More documents

Recommendations

Info

2.3 Rules The following rules are used throughout this specification to describe basic parsing constructs. The US-ASCII coded character set is defined by ANSI X3.4-1986 [5]. Parsed entities are constructed combinations of atoms or other entities as defined below. Atoms may be combined and repeated to form longer constructs. When there are constraints on the repetition of atoms, the constraints are expressed by a notation of the form: m * n where both m and n are integers. m represents the minimum allowed number of repetitions, and n represents the maximum. If m is omitted, it is presumed to be zero; if n is omitted, it is presumed to be infinite. For example, the syntactic construct 1*64ALPHANUM means a string of ALPHANUMs containing at least 1 and at most 64. When a parsing construct is represented by a string of entities, some of which are optional, the optional entities are enclosed in square brackets. For example, in the string error-number [error-code] the error-number entity is required, while the error-cod entity is optional. Elements separated by the vertical bar are alternatives. The entity description ALPHA | DIGIT means “either an ALPHA or a DIGIT”. 2.4 Atoms and Primitive Entities Note The definitions for ALPHA, CHAR, CTL, DIGIT , HEXDIG and OCTET are derived from RFC 2234. ALPHA CHAR CTL DIGIT HEXDIG OCTET ::= %x41-5A | %x61-7A ; A-Z | a-z ::= %x01-7F ; ANY 7-BIT US-ASCII CHARACTER, ; EXCLUDING NUL ::= %x00-1F | %x7F ; controls ::= %x30-39 ; 0-9 ::= DIGIT | "A" | "B" | "C" | "D" | "E" | "F" ::= %x00-FF ; any 8-bit sequence of data 2-2 Real Estate Transaction Specification Version 1.7.2
BOOLEAN ::= TRUE | FALSE TRUE ::= “1” FALSE ::= “0” RETSID RETSNAME IDALPHANUM ::= 1*32ALPHANUM ::= 1*64IDALPHANUM ::= ALPHANUM | “_” ALPHANUM ::= ALPHA | DIGIT SQLFIELDNAME ::= ALPHA *31ALPHANUM CR ::= LF ::= SP ::= HT ::= = 0 ::= NULL | POSITIVENUM ; null or >= 1 ::= “0” | POSITIVENUM ; also known as cardinal numbers or counting numbers ; consisting of integers greater than 0 ::= %x31-39 ; 1-9 ::= ::= NONZERODIGIT *DIGIT ; > 0 ::= “-1” | NONNEGATIVENUM ; Version 1.7.2 2-3
Page 1: Real Estate Data Interchange Standa
Page 4 and 5: Required Response Arguments . . . .
Page 6 and 7: iv Real Estate Transaction Specific
Page 8 and 9: vi Real Estate Transaction Specific
Page 10 and 11: viii Real Estate Transaction Specif
Page 12 and 13: SHOULD This word or the adjective
Page 14 and 15: 1-4 Real Estate Transaction Specifi
Page 18 and 19: Note TEXT ::= Implementers are cau
Page 20 and 21: |"25" %x30-35 ; 250-255 reg-name ::
Page 22 and 23: 3.1.3 Response Bodies 3.2 Request F
Page 24 and 25: 3.5 Response Format requires user-a
Page 26 and 27: Example: Content-Type Example: RETS
Page 28 and 29: 3.9 General Status Codes Any of the
Page 30 and 31: 3-10 Real Estate Transaction Specif
Page 32 and 33: compliant server MAY support only H
Page 34 and 35: oker-code ::= 1*24ALPHANUM 4.7.2 Me
Page 36 and 37: 4.8.3 Office List Information passw
Page 38 and 39: 4.11 Reply Codes section 5.1.1) for
Page 40 and 41: The qvalue is used to specify the d
Page 42 and 43: Object-ID The object number being r
Page 44 and 45: --simple boundary-- 5.11.2 Error Ha
Page 48 and 49: that users would read or see the me
Page 50 and 51: 7.2 Search Terminology 7.2.1 Field
Page 52 and 53: If the client requests STANDARD-XML
Page 54 and 55: 7.4.7 StandardNames This would mean
Page 56 and 57: 7.7 Query language 7.7.1 Query lang
Page 58 and 59: 7.7.3 Sub-queries the same as 2 or
Page 60 and 61: 7-12 Real Estate Transaction Specif
Page 64 and 65: 9.5 Reply Codes 9.6 Encryption Key
Page 66 and 67:
database is not updated. If this en
Page 68 and 69:
10.5.2 Warning block 10.6 Validatio
Page 70 and 71:
10-6 Real Estate Transaction Specif
Page 72 and 73:
System Resource Class Table Foreign
Page 74 and 75:
corresponds to the similarly-positi
Page 76 and 77:
Table 11-4 Well-Known Resource Name
Page 78 and 79:
11.2.3 Foreign Keys Table 11-6 Meta
Page 80 and 81:
Table 11-8 Metadata Content: Foreig
Page 82 and 83:
COMPACT header tag: METADATA-TABLE
Page 84 and 85:
Table 11-12 Metadata Content - Tabl
Page 86 and 87:
11.3.3 Update A given data resource
Page 88 and 89:
11.4 Metadata Format for Shared Ele
Page 90 and 91:
COMPACT header tag: METADATA-LOOKUP
Page 92 and 93:
11.4.6 Update Help RETS Regular Exp
Page 94 and 95:
Table 11-32 Metadata Content: Valid
Page 96 and 97:
during expression evaluation, field
Page 98 and 99:
COMPACT header tag: METADATA-VALIDA
Page 100 and 101:
11-30 Real Estate Transaction Speci
Page 102 and 103:
“COMPACT” means a table descrip
Page 104 and 105:
Table 12-1 GetMetadata Reply Codes
Page 106 and 107:
13.3 Multivalued Fields COMPACT for
Page 108 and 109:
14.3 Session 14.4 Termination then
Page 110 and 111:
NOTE RETS 1.7.2 requires all serve
Page 112 and 113:
Page 114 and 115:
Stuart Schuessler Libor Viktorin Ma
Page 116 and 117:
Page 118 and 119:
[15] Kristol, D. and Montulli, L.,
Page 120 and 121:
Table A-1 DTD References RETS Metad
Page 122 and 123:
B.3 Foreign Keys B.4 Class 2002-03-
Page 124 and 125:
Type: METADATA-UPDATE_TYPE ID: Prop
Page 126 and 127:
B.14 Validation Lookup →UpdateHe
Page 128 and 129:
B-8 Real Estate Transaction Specifi
Page 130 and 131:
Table C-1 Consolidated list of RETS
Page 132 and 133:
Table C-1 Consolidated list of RETS
Page 134 and 135:
D.2 Datatype Character Interpretati
Page 136 and 137:
E-2 Real Estate Transaction Specifi
Page 138 and 139:
IOC-2 Real Estate Transaction Speci
Page 140 and 141:
J Justification, text, specifying,
Page 142:
IX-4 Real Estate Transaction Specif
show all

Specification - RETS

Create successful ePaper yourself

Delete template?

Save as template?