idnits 2.17.1 draft-duerst-anno-link-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 7, 2011) is 4615 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 5988 (Obsoleted by RFC 8288) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Duerst 3 Internet-Draft Aoyama Gakuin University 4 Intended status: Informational September 7, 2011 5 Expires: March 10, 2012 7 The 'annotation-server' Link Relation Type 8 draft-duerst-anno-link-01 10 Abstract 12 This document defines the 'annotation-server' Link Relation Type to 13 suggest a server to store and retreive Web annotations. 15 Status of this Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on March 10, 2012. 38 Copyright Notice 40 Copyright (c) 2011 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the BSD License. 53 This document may contain material from IETF Documents or IETF 54 Contributions published or made publicly available before November 55 10, 2008. The person(s) controlling the copyright in some of this 56 material may not have granted the IETF Trust the right to allow 57 modifications of such material outside the IETF Standards Process. 58 Without obtaining an adequate license from the person(s) controlling 59 the copyright in such materials, this document may not be modified 60 outside the IETF Standards Process, and derivative works of it may 61 not be created outside the IETF Standards Process, except to format 62 it for publication as an RFC or to translate it into languages other 63 than English. 65 Table of Contents 67 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 2. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 69 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 70 4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 4 71 5. Normative References . . . . . . . . . . . . . . . . . . . . . 4 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 74 1. Overview 76 Various mechanisms have been proposed for creating annotations to Web 77 pages (hereafter called "Web annotations"). While some such 78 mechanisms are tightly integrated with the Web page itself, others, 79 such as Annnotea [Annotea], allow storing Web annonations on 80 arbitrary third-party servers. This creates a lot of independence 81 and flexibility, but also risks that annotations for the same Web 82 page are scattered among various servers which cannot easily be 83 found. 85 To make it easier to find and place annotations for a given Web page 86 on annotation servers, this document defines the 'annotation-server' 87 Link Relation Type [RFC5988]. The link target is a suggestion for 88 which server to use to find existing annotations and to place new 89 annotations for the link context. This Link Relation Type does not 90 constrain the protocol to be used to store and retreive annotations. 91 A future version of this document might propose additional 92 application data to specify protocol details. 94 2. Security Considerations 96 Please see the security considerations section of [RFC5988]. 98 3. IANA Considerations 100 IANA is requested to register the following Link Relation Type in the 101 Link Relation Type Registry [RFC5988]. The registration template is 102 as follows: 104 Relation Name: 105 annotation-server 107 Description: 108 Designates an annotation server used to store annotations 109 for the link's context. 111 Reference: 112 RFC YYYY [RFC Editor: Please replace with actual RFC number.] 114 Notes: 115 currently none 117 Application Data: 118 currently none 120 4. Acknowledgments 122 Keita Mochizuki implemented the 'annotation-server' link relation 123 type in Annoplus. 125 5. Normative References 127 [Annotea] Swick, R., Prud'hommeaux, E., Koivunen, M., and J. Kahan, 128 "Annotea Protocols", December 2002. 130 [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010. 132 Author's Address 134 Martin Duerst (Note: Please write "Duerst" with u-umlaut wherever 135 possible, for example as "Dürst" in XML and HTML.) 136 Aoyama Gakuin University 137 5-10-1 Fuchinobe 138 Chuo-ku 139 Sagamihara, Kanagawa 252-5258 140 Japan 142 Phone: +81 42 759 6329 143 Fax: +81 42 759 6495 144 Email: duerst@it.aoyama.ac.jp 145 URI: http://www.sw.it.aoyama.ac.jp/D%C3%BCrst/