RETS Change Proposal 43: Capability URL Rules
|
| Author: David Terrell |
| Organization: Center for REALTORŪ Technology |
| Telephone: |
| Address: 430 N. Michigan Ave., Floor 6, Chicago IL, 60611-4087 |
| Email: dterrell@crt.realtors.org |
| Status: Proposal |
| Date: 11/07/2003 |
| Proposal Version: 1.7 |
| 1. Synopsis |
| Capabilty URL normalization rules are defined. |
| 2. Rationale |
| The current set of rules are vague (what if the Login= URL is relative?) and could be better. |
| 3. Proposal |
| The paragraph that starts "URLs may be either absolute or relative..." in section 4.10 is changed to be
URLs other than the Login URL maybe 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. Specifically, the Login URL specified in the login response should be used as the base URL as referred to in RFC 2396, section 5.1.1 ("base URI within document context"). |
| 4. Development Impact |
| This gives clients an easier, more standards-based way of normalizing URLs. |
| 5. Compatibility |
| These scheme is backwards compatible from a client perspectivee with rules specified previously, depending on your interpretation of the phrase "relative to the Login-URL". It does permit servers to send less-specific URLs than before (i.e. just "getmetadata" instead of "/path/to/getmetadata"). Server vendors SHOULD be careful in sending such URLs only when they are reasonably certain they will be properly understood. |
| 6. Proof/Need of Concept Examples |
| None. |