INTERNET-DRAFT M. Yevstifeyev
Intended Status: Informational January 4, 2012
Expires: July 7, 2012
The 'disclosure' Link Relation Type
draft-yevstifeyev-disclosure-relation-01
Abstract
This document specifies the 'disclosure' link relation type. It
designates a list of patent disclosures made with respect to the
material for which such relation type is specified.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright and License Notice
Copyright (c) 2012 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
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.
Yevstifeyev Expires July 7, 2012 [Page 1]
INTERNET DRAFT 'disclosure' Link Relation Type January 4, 2012
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 2
2. 'disclosure' Link Relation Type . . . . . . . . . . . . . . . . 2
2.1. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
5. Normative References . . . . . . . . . . . . . . . . . . . . . 4
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
RFC 5988 [RFC5988] defined a way of indicating relationships between
resources on the Web. This document specifies the 'disclosure' link
relation type. It designates a list of patent disclosures made with
respect to the material for which such relation type is specified.
Please note that the term "IPR disclosure" should be considered to be
synonymous to "patent disclosure" for the purposes of 'disclosure'
link relation type semantics.
The 'disclosure' link relation type has been in active use of W3C,
which requires all the W3C documents to contain a link to a list of
patent disclosures referenced with the relation type being defined.
However, it has long been used with no proper specification and
registration. This document is to accomplish this gap. It formally
specifies the existing practice of use of 'disclosure' link relation
type and registers it in the registry created by RFC 5988.
Please note that 'disclosure' relation type designates a different
resource that 'copyright' type does; the latter refers to the
copyright statement while the former is used to reference patent
disclosure. Please visit RFC 5988 [RFC5988] for more information on
'copyright' relation type.
1.1. Terminology
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 RFC 2119 [RFC2119].
2. 'disclosure' Link Relation Type
Whenever the 'disclosure' relation type is used, the target IRI
[RFC5988] MUST refer to a list of patent disclosures (IPR
disclosures) made with respect to the material referenced by context
IRI. This also covers the case of empty list and a list containing
Yevstifeyev Expires July 7, 2012 [Page 2]
INTERNET DRAFT 'disclosure' Link Relation Type January 4, 2012
one entry.
2.1. Examples
This section provides an example of possible use of 'disclosure'
relation type.
If the page contains a list of
patent disclosures made with respect to the specification found at
, the latter would have
the following fragment of HTML source code:
...
Please visit
the IPR page for the list of patent disclosures made with
respect to this specification.
...
Or, in the case of Link header field, the HTTP response would contain
the following header field:
Link: ; rel="disclosure";
title="Patent Disclosures List"
(Please note that the actual header field will not contain the line
break and spaces after 'rel' parameter.)
3. Security Considerations
The 'disclosure' relation type is truly believed not to raise any new
security issues which are not discussed in RFC 5988 for generic use
of Web linking mechanism.
4. IANA Considerations
IANA is asked to register the 'disclosure' link relation type in the
corresponding registry, with reference to this document, using the
following template:
o Relation name: disclosure
o Description: refers to a list of patent disclosures made with
respect to material for which 'disclosure' relation is specified
o Reference: RFC xxxx
Yevstifeyev Expires July 7, 2012 [Page 3]
INTERNET DRAFT 'disclosure' Link Relation Type January 4, 2012
5. 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.
Appendix A. Acknowledgments
Thanks to Bjoern Hoehrmann for noticing that 'disclosure' relation is
not properly specified and, correspondingly, initiating this work.
The author would also like to acknowledge the contributions of (in
alphabetical order) Bjoern Hoehrmann, John Klensin, Subramanian
Moonesamy, Julian Reschke, Thomas Roessler, Martin Thomson, and
Juergen Quittek to this document.
Authors' Addresses
Mykyta Yevstifeyev
8 Kuzovkov St., Apt. 25
Kotovsk
Ukraine
EMail: evnikita2@gmail.com
Yevstifeyev Expires July 7, 2012 [Page 4]