< draft-yevstifeyev-disclosure-relation-01.txt		draft-yevstifeyev-disclosure-relation-02.txt >
	INTERNET-DRAFT M. Yevstifeyev		INTERNET-DRAFT M. Yevstifeyev
	Intended Status: Informational January 4, 2012		Intended Status: Informational January 4, 2012
	Expires: July 7, 2012		Expires: July 7, 2012
	The 'disclosure' Link Relation Type		The 'disclosure' Link Relation Type
	draft-yevstifeyev-disclosure-relation-01		draft-yevstifeyev-disclosure-relation-02
	Abstract		Abstract
	This document specifies the 'disclosure' link relation type. It		This document specifies the 'disclosure' link relation type. It
	designates a list of patent disclosures made with respect to the		designates a list of IPR disclosures made with respect to the
	material for which such relation type is specified.		material for which such relation type is specified.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as		other groups may also distribute working documents as
	skipping to change at page 2, line 21 ¶		skipping to change at page 2, line 21 ¶
	3. Security Considerations . . . . . . . . . . . . . . . . . . . . 3		3. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
	5. Normative References . . . . . . . . . . . . . . . . . . . . . 4		5. Normative References . . . . . . . . . . . . . . . . . . . . . 4
	Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 4		Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 4
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4
	1. Introduction		1. Introduction
	RFC 5988 [RFC5988] defined a way of indicating relationships between		RFC 5988 [RFC5988] defined a way of indicating relationships between
	resources on the Web. This document specifies the 'disclosure' link		resources on the Web. This document specifies the 'disclosure' link
	relation type. It designates a list of patent disclosures made with		relation type. It designates a list of IPR disclosures made with
	respect to the material for which such relation type is specified.		respect to the material for which such relation type is specified.
	Please note that the term "IPR disclosure" should be considered to be		Please note that the term "patent disclosure" should be considered to
	synonymous to "patent disclosure" for the purposes of 'disclosure'		be synonymous to "IPR disclosure" for the purposes of 'disclosure'
	link relation type semantics.		link relation type semantics, as patent disclosures are a subset of
			IPR disclosures.
	The 'disclosure' link relation type has been in active use of W3C,		The W3C already mandates the use of the 'disclosure' link relation
	which requires all the W3C documents to contain a link to a list of		type for links to patent disclosures in all its documents. However,
	patent disclosures referenced with the relation type being defined.		it has long been used with no proper specification and registration.
	However, it has long been used with no proper specification and		This document is to accomplish this gap and encourage wider use of
	registration. This document is to accomplish this gap. It formally		'disclosure' relation type. It formally specifies the existing
	specifies the existing practice of use of 'disclosure' link relation		practice of use of the link relation type and registers it in the
	type and registers it in the registry created by RFC 5988.		registry created by RFC 5988.
	Please note that 'disclosure' relation type designates a different		Please note that 'disclosure' relation type designates a different
	resource that 'copyright' type does; the latter refers to the		resource that 'copyright' type does; the latter refers to the
	copyright statement while the former is used to reference patent		copyright statement while the former is used to reference patent
	disclosure. Please visit RFC 5988 [RFC5988] for more information on		disclosure. Please visit RFC 5988 [RFC5988] for more information on
	'copyright' relation type.		'copyright' relation type.
	1.1. Terminology		1.1. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	2. 'disclosure' Link Relation Type		2. 'disclosure' Link Relation Type
	Whenever the 'disclosure' relation type is used, the target IRI		Whenever the 'disclosure' relation type is used, the resource at the
	[RFC5988] MUST refer to a list of patent disclosures (IPR		target IRI [RFC5988] MUST represent a list of patent disclosures made
	disclosures) made with respect to the material referenced by context		with respect to the material referenced by context IRI. This also
	IRI. This also covers the case of empty list and a list containing		covers the case of an empty list and a list containing one entry.
	one entry.
	2.1. Examples		2.1. Examples
	This section provides an example of possible use of 'disclosure'		This section provides an example of possible use of 'disclosure'
	relation type.		relation type.
	If the page <http://example.org/ipr/meta-spec/> contains a list of		If the page <http://example.org/ipr/meta-spec/> contains a list of
	patent disclosures made with respect to the specification found at		patent disclosures made with respect to the specification found at
	<http://example.org/specs/meta-spec/spec.html>, the latter would have		<http://example.org/specs/meta-spec/spec.html>, the latter would have
	the following fragment of HTML source code:		the following fragment of HTML source code:
	<html>		<html>
	...		...
	Please visit		Please visit
	<a rel="disclosure-list" href="http://example.org/ipr/meta-spec/">		<a rel="disclosure" href="http://example.org/ipr/meta-spec/">
	the IPR page</a> for the list of patent disclosures made with		the IPR page</a> for the list of patent disclosures made with
	respect to this specification.		respect to this specification.
	...		...
	</html>		</html>
	Or, in the case of Link header field, the HTTP response would contain		Or, in the case of Link header field, the HTTP response would contain
	the following header field:		the following header field:
	Link: <http://example.org/ipr/meta-spec/>; rel="disclosure";		Link: <http://example.org/ipr/meta-spec/>; rel="disclosure";
	title="Patent Disclosures List"		title="Patent Disclosures List"
	skipping to change at page 4, line 18 ¶		skipping to change at page 4, line 18 ¶
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010.		[RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010.
	Appendix A. Acknowledgments		Appendix A. Acknowledgments
	Thanks to Bjoern Hoehrmann for noticing that 'disclosure' relation is		Thanks to Bjoern Hoehrmann for noticing that 'disclosure' relation is
	not properly specified and, correspondingly, initiating this work.		not properly specified and, correspondingly, initiating this work.
	The author would also like to acknowledge the contributions of (in		The author would also like to acknowledge the contributions of (in
	alphabetical order) Bjoern Hoehrmann, John Klensin, Subramanian		alphabetical order) Bjoern Hoehrmann, John Klensin, Subramanian
	Moonesamy, Julian Reschke, Thomas Roessler, Martin Thomson, and		Moonesamy, Julian Reschke, Thomas Roessler, Peter Saint-Andre, Martin
	Juergen Quittek to this document.		Thomson, and Juergen Quittek to this document.
	Authors' Addresses		Authors' Addresses
	Mykyta Yevstifeyev		Mykyta Yevstifeyev
	8 Kuzovkov St., Apt. 25		8 Kuzovkov St., Apt. 25
	Kotovsk		Kotovsk
	Ukraine		Ukraine
	EMail: evnikita2@gmail.com		EMail: evnikita2@gmail.com
End of changes. 8 change blocks.
	21 lines changed or deleted		21 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/