Specification - RETS

[ServerInformation = server-information-URL CRLF]
[Update = update-URL CRLF]
Table 4-2
Parameter
action-URL
Capability URL Descriptions
change-password-URL
get-metadata-URL
get-object-URL
login-URL
login-complete-URL
logout-URL
search-URL
update-URL
server-information-URL
Purpose
A URL on which the client MUST perform a GET immediately after
login. This might include a bulletin or the notification of email. The
client application SHOULD provide a means for the user to view
the retrieved document. A server is not required to supply an
Action URL.
A URL for the ChangePassword transaction.
A URL for the Get Metadata transaction.
A URL for the Get Object transaction.
A URL for the Login Transaction. The client software should use
this URL the next time it performs a Login. If this URL is different
from the one currently stored by the client the client, MUST update
the stored one to the new one. This provides a mechanism to move
the Login server.
RESERVED
A URL for the Logout transaction.
A URL for the Search transaction.
A URL for the Update transaction.
A URL for the System Information transaction
The URLs in the capability-url-list may be specified in any order. Since the list is returned
in the body, servers MAY include whitespace between the parameter, equals sign and URL.
Clients SHOULD be prepared to receive the capability-url-list either with or without
whitespace in the response. The format of each URL follows the pattern defined in the URL
atom. In addition, the table is extensible; servers may define additional transactions for
clients to access. If a transaction is offered only to particular user agents, the keys for those
additional transactions MUST begin with the user-agent token, followed by a dash “-”,
followed by an implementation-defined function name. Note that this definition does not
permit spaces in the additional-transaction definition per the ABNF rules.
additional-transaction ::= (“X” | user-agent-token ) “-” function-name CRLF
user-agent-token ::=
function-name
Example:
Example:
::= 1*ALPHA
MLSWindows-special = /special_function
X-Delete = http://www.example.com:6103/deletemyrecord
A compliant client need not recognize any transaction that is not included in this
specification. If some extended transactions are offered to any user-agent, the keys for
those transactions MUST begin with an “X” followed by a dash, followed by an
implementation-defined function name. Server implementers who implement potentiallyunrestricted
extension transactions are urged to register their keys and service descriptions
on the RETS web site to encourage wider adoption.
URLs other than the Login URL may be relative URLs. The Login URL MUST be an
absolute URL. If a URL is not absolute, the client application should canonicalize it
according to the rules in RFC 2396, section 5. The “base URL” (as defined in RFC 2396,
Version 1.7.2 4-7