Network Working Group I. Dzmanashvili Internet-Draft May 26, 2013 Intended status: Informational Expires: November 27, 2013 The "property" and "context" Link Relations draft-property-and-context-link-relations-00 Abstract RFC 5988 [RFC5988] defined the way of indicating resources on the Web. This specification defines link relation types that may be used to express the relationships between a resource and associated properties or between a resource and it's context. Editorial Note (To be removed by RFC Editor) Distribution of this document is unlimited. Comments should be sent to the IETF Apps-Discuss mailing list (see ). Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on November 27, 2013. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents Dzmanashvili Expires November 27, 2013 [Page 1] Internet-Draft The property and context Link Relations May 2013 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3 3. Link Relations . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. The "property" Link Relation Type . . . . . . . . . . . . . 4 3.2. The "context" Link Relation Type . . . . . . . . . . . . . 5 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 4.1. The Link Relation Registration "property" . . . . . . . . . 6 4.2. The Link Relation Registration "context" . . . . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 6. Internationalisation Considerations . . . . . . . . . . . . . . 7 7. Normative References . . . . . . . . . . . . . . . . . . . . . 7 Dzmanashvili Expires November 27, 2013 [Page 2] Internet-Draft The property and context Link Relations May 2013 1. Introduction RFC 5988 [RFC5988] defined the way of indicating resources on the Web. This specification defines link relation types that may be used to express the relationships between a resource and associated properties or between a resource and it's context. The "property" and "context" link relations are intentionally generic, and they can be used with multiple media types in a wide variety of use cases. 2. Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. Dzmanashvili Expires November 27, 2013 [Page 3] Internet-Draft The property and context Link Relations May 2013 3. Link Relations The following link relations are defined. 3.1. The "property" Link Relation Type When included in a response, the "property" link relation identifies a target resource that represents a property of the context resource. For example, if a resource represents a photo, that same resource may include one ore more links to resources that represent properties of that photo. Example expressed as a Link header field: HTTP/1.1 200 OK Content-Type: image/jpeg Content-Length: ... Link: ; rel="property"; title="...", ; rel="property"; title="..." Or expressed as an HTML document: ... Dzmanashvili Expires November 27, 2013 [Page 4] Internet-Draft The property and context Link Relations May 2013 3.2. The "context" Link Relation Type When included in a response, the "context" link relation identifies a target resource that represents a context document of which the context resource is a member. For example, if a resource represents the property of a photo, that same resource may include link to a resource which the property belongs. Example expressed as a Link header field: HTTP/1.1 200 OK Content-Type: text/plain Content-Length: ... Link: <...>; rel="context"; title="...", <...>; rel="self"; title="..." Or expressed as an HTML document: ... Dzmanashvili Expires November 27, 2013 [Page 5] Internet-Draft The property and context Link Relations May 2013 4. IANA Considerations IANA is asked to register the "property" and "context" link relations below as per [RFC5988]. 4.1. The Link Relation Registration "property" Relation Name: property Description: The target IRI points to a resource that is a property of the resource represented by the context IRI. Security considerations: Automated agents should take care when this relation crosses administrative domains (e.g., the URI has a different authority than the current document). Reference: See Section 3. 4.2. The Link Relation Registration "context" Relation Name: context Description: The target IRI points to a resource of which the context resource is a member. Security considerations: Automated agents should take care when this relation crosses administrative domains (e.g., the URI has a different authority than the current document). Reference: See Section 3. Dzmanashvili Expires November 27, 2013 [Page 6] Internet-Draft The property and context Link Relations May 2013 5. Security Considerations See Section 7 of RFC5988 [RFC5988]. 6. Internationalisation Considerations See Section 8 of RFC5988 [RFC5988]. 7. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010. Author's Address Ioseb Dzmanashvili EMail: ioseb.dzmanashvili@gmail.com Dzmanashvili Expires November 27, 2013 [Page 7]