draft-ietf-calext-ical-relations-02.txt   draft-ietf-calext-ical-relations-03.txt 
Network Working Group M. Douglass Network Working Group M. Douglass
Internet-Draft Spherical Cow Group Internet-Draft Spherical Cow Group
Updates: 5545 (if approved) February 10, 2017 Updates: 5545 (if approved) October 11, 2017
Intended status: Standards Track Intended status: Standards Track
Expires: August 14, 2017 Expires: April 14, 2018
Support for iCalendar Relationships Support for iCalendar Relationships
draft-ietf-calext-ical-relations-02 draft-ietf-calext-ical-relations-03
Abstract Abstract
This specification updates RELATED-TO defined in [RFC5545] and This specification updates RELATED-TO defined in [RFC5545] and
introduces new iCalendar properties LINK, STRUCTURED-CATEGORY and introduces new iCalendar properties LINK, CONCEPT and REFID to allow
REFID to allow better linking and grouping of iCalendar components better linking and grouping of iCalendar components and related data.
and related data.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted 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). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 14, 2017. This Internet-Draft will expire on April 14, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Structured iCalendar relationships . . . . . . . . . . . 3 1.1. Structured iCalendar relationships . . . . . . . . . . . 3
1.2. Grouped iCalendar relationships . . . . . . . . . . . . . 3 1.2. Grouped iCalendar relationships . . . . . . . . . . . . . 3
1.3. Structured category relationships . . . . . . . . . . . . 3 1.3. Concept relationships . . . . . . . . . . . . . . . . . . 3
1.4. Linked relationships . . . . . . . . . . . . . . . . . . 4 1.4. Linked relationships . . . . . . . . . . . . . . . . . . 4
1.5. Caching and offline use . . . . . . . . . . . . . . . . . 4 1.5. Caching and offline use . . . . . . . . . . . . . . . . . 5
1.6. Conventions Used in This Document . . . . . . . . . . . . 5 1.6. Conventions Used in This Document . . . . . . . . . . . . 5
2. Reference Types . . . . . . . . . . . . . . . . . . . . . . . 5 2. Reference Types . . . . . . . . . . . . . . . . . . . . . . . 5
3. Link Relation Types . . . . . . . . . . . . . . . . . . . . . 5 3. Link Relation Types . . . . . . . . . . . . . . . . . . . . . 5
4. Redefined Relation Type Value . . . . . . . . . . . . . . . . 5 4. Redefined Relation Type Value . . . . . . . . . . . . . . . . 5
5. New Property Parameters . . . . . . . . . . . . . . . . . . . 8 5. New Property Parameters . . . . . . . . . . . . . . . . . . . 8
5.1. Rel . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 5.1. Rel . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.2. Gap . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.2. Gap . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6. New Value Data Types . . . . . . . . . . . . . . . . . . . . 9 6. New Value Data Types . . . . . . . . . . . . . . . . . . . . 9
7. New Properties . . . . . . . . . . . . . . . . . . . . . . . 10 7. New Properties . . . . . . . . . . . . . . . . . . . . . . . 10
7.1. Structured-Category . . . . . . . . . . . . . . . . . . . 10 7.1. Concept . . . . . . . . . . . . . . . . . . . . . . . . . 10
7.2. Link . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7.2. Link . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.3. Refid . . . . . . . . . . . . . . . . . . . . . . . . . . 13 7.3. Refid . . . . . . . . . . . . . . . . . . . . . . . . . . 13
8. Redefined RELATED-TO Property . . . . . . . . . . . . . . . . 13 8. Redefined RELATED-TO Property . . . . . . . . . . . . . . . . 13
8.1. RELATED-TO . . . . . . . . . . . . . . . . . . . . . . . 14 8.1. RELATED-TO . . . . . . . . . . . . . . . . . . . . . . . 14
9. Security Considerations . . . . . . . . . . . . . . . . . . . 16 9. Security Considerations . . . . . . . . . . . . . . . . . . . 16
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
10.1. iCalendar Property Registrations . . . . . . . . . . . . 16 10.1. iCalendar Property Registrations . . . . . . . . . . . . 16
10.2. iCalendar Property Parameter Registrations . . . . . . . 16 10.2. iCalendar Property Parameter Registrations . . . . . . . 16
10.3. iCalendar Value Data Type Registrations . . . . . . . . 16 10.3. iCalendar Value Data Type Registrations . . . . . . . . 16
10.4. iCalendar RELTYPE Value Registrations . . . . . . . . . 17 10.4. iCalendar RELTYPE Value Registrations . . . . . . . . . 17
10.5. New Reference Type Registration . . . . . . . . . . . . 17 10.5. New Reference Type Registration . . . . . . . . . . . . 17
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17
12. Normative References . . . . . . . . . . . . . . . . . . . . 18 12. Normative References . . . . . . . . . . . . . . . . . . . . 18
Appendix A. Change log . . . . . . . . . . . . . . . . . . . . . 18
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 19 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
iCalendar entities often need to be related to each other or to iCalendar entities often need to be related to each other or to
associated meta-data. These relationships can take the following associated meta-data. These relationships can take the following
forms forms
Structured iCalendar: iCalendar entities are related to each other Structured iCalendar: iCalendar entities are related to each other
in some structured way, for example as parent, sibling, before, in some structured way, for example as parent, sibling, before,
skipping to change at page 3, line 37 skipping to change at page 3, line 35
this key. This may be, for example, to identify the tasks associated this key. This may be, for example, to identify the tasks associated
with a given project without having to communicate the task structure with a given project without having to communicate the task structure
of the project, or, for example, in a package delivery system all of the project, or, for example, in a package delivery system all
tasks associated to a specific package. tasks associated to a specific package.
As such, the presence of a REFID property imparts no meaning to the As such, the presence of a REFID property imparts no meaning to the
event. It is merely a key to allow retrieval. This is distinct from event. It is merely a key to allow retrieval. This is distinct from
categorisation which, while allowing grouping also adds meaning to categorisation which, while allowing grouping also adds meaning to
the entity to which it is attached. the entity to which it is attached.
1.3. Structured category relationships 1.3. Concept relationships
The introduction of STRUCTURED-CATEGORY allows a more structured The name CONCEPT is used by the Simple Knowledge Organization System
approach to categorization, with the possibility of namespaced and defined in [W3C.CR-skos-reference-20090317]. This more accurately
path-like values. Unlike REFID the category imparts some meaning. defines what we mean by a catgeory. It's not the words but the
It is assumed that the value of this property will reference a well meaning.
The introduction of CONCEPT allows a more structured approach to
categorization, with the possibility of namespaced and path-like
values. Unlike REFID the CONCEPT property imparts some meaning. It
is assumed that the value of this property will reference a well
defined category. defined category.
The current [RFC5545] CATEGORY property is used as a free form The current [RFC5545] CATEGORY property is used as a free form
'tagging' field. As such it is difficult to establish formal 'tagging' field. As such it is difficult to establish formal
relationships between components based on their category. relationships between components based on their category.
Rather than attempt to add semantics to the current property it Rather than attempt to add semantics to the current property it
seeems best to continue its usage as an informal tag and establish a seeems best to continue its usage as an informal tag and establish a
new property with more constraints. new property with more constraints.
skipping to change at page 6, line 13 skipping to change at page 6, line 15
Format Definition: Format Definition:
This property parameter is defined by the following notation: This property parameter is defined by the following notation:
reltypeparam = "RELTYPE" "=" reltypeparam = "RELTYPE" "="
("PARENT" ; Parent relationship - Default ("PARENT" ; Parent relationship - Default
/ "CHILD" ; Child relationship / "CHILD" ; Child relationship
/ "SIBLING" ; Sibling relationship / "SIBLING" ; Sibling relationship
/ "DEPENDS-ON" ; refers to previous task / "DEPENDS-ON" ; refers to previous task
/ "REFID" ; Relationship based on REFID / "REFID" ; Relationship based on REFID
/ "STRUCTURED-CATEGORY" / "CONCEPT"
; Relationship based on STRUCTURED-CATEGORY ; Relationship based on CONCEPT
/ "FINISHTOSTART" ; Temporal relationship / "FINISHTOSTART" ; Temporal relationship
/ "FINISHTOFINISH" ; Temporal relationship / "FINISHTOFINISH" ; Temporal relationship
/ "STARTTOFINISH" ; Temporal relationship / "STARTTOFINISH" ; Temporal relationship
/ "STARTTOSTART" ; Temporal relationship / "STARTTOSTART" ; Temporal relationship
/ iana-token ; Some other IANA-registered / iana-token ; Some other IANA-registered
; iCalendar relationship type ; iCalendar relationship type
/ x-name) ; A non-standard, experimental / x-name) ; A non-standard, experimental
; relationship type ; relationship type
Description: This parameter can be specified on a property that Description: This parameter can be specified on a property that
skipping to change at page 7, line 9 skipping to change at page 7, line 11
RELTYPE=DEPENDS-ON: Indicates that the current calendar component RELTYPE=DEPENDS-ON: Indicates that the current calendar component
depends on the referenced calendar component in some manner. For depends on the referenced calendar component in some manner. For
example a task may be blocked waiting on the other, referenced, example a task may be blocked waiting on the other, referenced,
task. task.
RELTYPE=REFID: Establishes a reference from the current component to RELTYPE=REFID: Establishes a reference from the current component to
components with a REFID property which matches the value given in components with a REFID property which matches the value given in
the associated RELATED-TO property. the associated RELATED-TO property.
RELTYPE=STRUCTURED-CATEGORY: Establishes a reference from the RELTYPE=CONCEPT: Establishes a reference from the current component
current component to components with a STRUCTURED-CATEGORY to components with a CONCEPT property which matches the value
property which matches the value given in the associated RELATED- given in the associated RELATED-TO property.
TO property.
RELTYPE=FINISHTOSTART: Task-B cannot start until Task-A finishes. RELTYPE=FINISHTOSTART: Task-B cannot start until Task-A finishes.
For example, when sanding is complete, painting can begin. For example, when sanding is complete, painting can begin.
============ ============
| Task-A |--+ | Task-A |--+
============ | ============ |
| |
V V
============ ============
skipping to change at page 9, line 16 skipping to change at page 9, line 16
REL=SOURCE: identifies the source of the event information. REL=SOURCE: identifies the source of the event information.
Registration: These relation types are registered in [RFC5988] Registration: These relation types are registered in [RFC5988]
5.2. Gap 5.2. Gap
Parameter name: GAP Parameter name: GAP
Purpose: To specify the length of the gap, positive or negative Purpose: To specify the length of the gap, positive or negative
between two temporally related components. between two temporaly related components.
Format Definition: Format Definition:
This parameter is defined by the following notation: This parameter is defined by the following notation:
gapparam = "GAP" "=" dur-value gapparam = "GAP" "=" dur-value
Description: This parameter MAY be specified on the RELATED-TO Description: This parameter MAY be specified on the RELATED-TO
property, and defines the duration of time between the predecessor property, and defines the duration of time between the predecessor
and successor in an interval. When positive it defines the lag and successor in an interval. When positive it defines the lag
skipping to change at page 10, line 7 skipping to change at page 10, line 7
with the VALUE property parameter: with the VALUE property parameter:
UID VALUE=UID indicates that the associated value is the UID for a UID VALUE=UID indicates that the associated value is the UID for a
component. component.
REFERENCE VALUE=REFERENCE indicates that the associated value is an REFERENCE VALUE=REFERENCE indicates that the associated value is an
xpointer referencing an associated XML artifact. xpointer referencing an associated XML artifact.
7. New Properties 7. New Properties
7.1. Structured-Category 7.1. Concept
Property name: STRUCTURED-CATEGORY Property name: CONCEPT
Purpose: This property defines the formal categories for a calendar Purpose: This property defines the formal categories for a calendar
component. component.
Value type: URI Value type: URI
Property Parameters: IANA, and non-standard parameters can be Property Parameters: IANA, and non-standard parameters can be
specified on this property. specified on this property.
Conformance: This property can be specified zero or more times in Conformance: This property can be specified zero or more times in
any iCalendar component. any iCalendar component.
Description: This property is used to specify formal categories or Description: This property is used to specify formal categories or
classifications of the calendar component. The values are useful classifications of the calendar component. The values are useful
in searching for a calendar component of a particular type and in searching for a calendar component of a particular type and
category. category.
Within the "VEVENT", "VTODO", or "VJOURNAL" calendar components, Within the "VEVENT", "VTODO", or "VJOURNAL" calendar components,
more than one formal category can be specified by using multiple more than one formal category can be specified by using multiple
properties. CONCEPT properties.
This categorization is distinct from the more informal "tagging" This categorization is distinct from the more informal "tagging"
of components provided by the existing CATEGORIES property. It is of components provided by the existing CATEGORIES property. It is
expected that the value of the STRUCTURED-CATEGORY property will expected that the value of the CONCEPT property will reference an
reference an external resource which provides information about external resource which provides information about the
the categorization. categorization.
Possible category resources are the various proprietary systems,
for example Library of Congress, or an open source such as
dmoz.org.
In addition, a structured URI value allows for hierarchical In addition, a structured URI value allows for hierarchical
categorization of events. categorization of events.
Possible category resources are the various proprietary systems,
for example Library of Congress, or an open source derived from
something like the dmoz.org data.
Format Definition: Format Definition:
This property is defined by the following notation: This property is defined by the following notation:
structured-category = "STRUCTURED-CATEGORY" structcatparam ":" concept = "CONCEPT" conceptparam ":"
uri CRLF uri CRLF
structcatparam = *( conceptparam = *(
; ;
; The following is OPTIONAL, ; The following is OPTIONAL,
; and MAY occur more than once. ; and MAY occur more than once.
; ;
(";" other-param) (";" other-param)
; ;
) )
Example: Example:
The following is an example of this property. It points to a server The following is an example of this property. It points to a server
acting as the source for the calendar object. acting as the source for the calendar object.
STRUCTURED-CATEGORY:http://example.com/event-types/sports SCONCEPT:http://example.com/event-types/sports
STRUCTURED-CATEGORY:http://example.com/event-types/arts/music CONCEPT:http://example.com/event-types/arts/music
STRUCTURED-CATEGORY:http://example.com/task-types/delivery CONCEPT:http://example.com/task-types/delivery
7.2. Link 7.2. Link
Property name: LINK Property name: LINK
Purpose: This property provides a reference to external information Purpose: This property provides a reference to external information
about a component. about a component.
Value type: URI, TEXT or REFERENCE Value type: URI, TEXT or REFERENCE
skipping to change at page 16, line 11 skipping to change at page 16, line 11
RELATED-TO;VALUE=URI;RELTYPE=STARTTOFINISH: RELATED-TO;VALUE=URI;RELTYPE=STARTTOFINISH:
http://example.com/caldav/user/jb/cal/ http://example.com/caldav/user/jb/cal/
19960401-080045-4000F192713.ics 19960401-080045-4000F192713.ics
9. Security Considerations 9. Security Considerations
Applications using the LINK property need to be aware of the risks Applications using the LINK property need to be aware of the risks
entailed in using the URIs provided as values. See [RFC3986] for a entailed in using the URIs provided as values. See [RFC3986] for a
discussion of the security considerations relating to URIs. discussion of the security considerations relating to URIs.
The STRUCTURED-CATEGORY and redefined RELATED-TO property have the The CONCEPT and redefined RELATED-TO property have the same issues in
same issues in that values may be URIs. that values may be URIs.
10. IANA Considerations 10. IANA Considerations
10.1. iCalendar Property Registrations 10.1. iCalendar Property Registrations
The following iCalendar property names have been added to the The following iCalendar property names have been added to the
iCalendar Properties Registry defined in Section 8.3.2 of [RFC5545] iCalendar Properties Registry defined in Section 8.3.2 of [RFC5545]
+---------------------+---------+-------------+ +----------+---------+-------------+
| Property | Status | Reference | | Property | Status | Reference |
+---------------------+---------+-------------+ +----------+---------+-------------+
| LINK | Current | Section 7.2 | | CONCEPT | Current | Section 7.1 |
| REFID | Current | Section 7.3 | | LINK | Current | Section 7.2 |
| STRUCTURED-CATEGORY | Current | Section 7.1 | | REFID | Current | Section 7.3 |
+---------------------+---------+-------------+ +----------+---------+-------------+
10.2. iCalendar Property Parameter Registrations 10.2. iCalendar Property Parameter Registrations
The following iCalendar property parameter names have been added to The following iCalendar property parameter names have been added to
the iCalendar Parameters Registry defined in Section 8.3.3 of the iCalendar Parameters Registry defined in Section 8.3.3 of
[RFC5545] [RFC5545]
+-----------+---------+-------------+ +-----------+---------+-------------+
| Parameter | Status | Reference | | Parameter | Status | Reference |
+-----------+---------+-------------+ +-----------+---------+-------------+
skipping to change at page 17, line 17 skipping to change at page 17, line 17
| UID | Current | Section 6 | | UID | Current | Section 6 |
| REFERENCE | Current | Section 6 | | REFERENCE | Current | Section 6 |
+-----------------+---------+-----------+ +-----------------+---------+-----------+
10.4. iCalendar RELTYPE Value Registrations 10.4. iCalendar RELTYPE Value Registrations
The following iCalendar "RELTYPE" values have been added to the The following iCalendar "RELTYPE" values have been added to the
iCalendar Relationship Types Registry defined in Section 8.3.8 of iCalendar Relationship Types Registry defined in Section 8.3.8 of
[RFC5545] [RFC5545]
+---------------------+---------+-----------+ +-------------------+---------+-----------+
| Parameter | Status | Reference | | Relationship Type | Status | Reference |
+---------------------+---------+-----------+ +-------------------+---------+-----------+
| DEPENDS-ON | Current | Section 4 | | DEPENDS-ON | Current | Section 4 |
| REFID | Current | Section 4 | | REFID | Current | Section 4 |
| STRUCTURED-CATEGORY | Current | Section 4 | | CONCEPT | Current | Section 4 |
| FINISHTOSTART | Current | Section 4 | | FINISHTOSTART | Current | Section 4 |
| FINISHTOFINISH | Current | Section 4 | | FINISHTOFINISH | Current | Section 4 |
| STARTTOFINISH | Current | Section 4 | | STARTTOFINISH | Current | Section 4 |
| STARTTOSTART | Current | Section 4 | | STARTTOSTART | Current | Section 4 |
+---------------------+---------+-----------+ +-------------------+---------+-----------+
10.5. New Reference Type Registration 10.5. New Reference Type Registration
The following link relation values have been added to the Reference The following link relation values have been added to the Reference
Types Registry defined in Section 6.2.2 of [RFC5988] Types Registry defined in Section 6.2.2 of [RFC5988]
+--------+---------+-------------+ +--------+---------+-------------+
| Name | Status | Reference | | Name | Status | Reference |
+--------+---------+-------------+ +--------+---------+-------------+
| SOURCE | Current | Section 5.1 | | SOURCE | Current | Section 5.1 |
skipping to change at page 18, line 15 skipping to change at page 18, line 15
12. Normative References 12. Normative References
[I-D.daboo-caldav-attachments] [I-D.daboo-caldav-attachments]
Daboo, C. and A. Quillaud, "CalDAV Managed Attachments", Daboo, C. and A. Quillaud, "CalDAV Managed Attachments",
draft-daboo-caldav-attachments-03 (work in progress), draft-daboo-caldav-attachments-03 (work in progress),
February 2014. February 2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005, RFC 3986, DOI 10.17487/RFC3986, January 2005,
<http://www.rfc-editor.org/info/rfc3986>. <https://www.rfc-editor.org/info/rfc3986>.
[RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and [RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and
Scheduling Core Object Specification (iCalendar)", Scheduling Core Object Specification (iCalendar)",
RFC 5545, DOI 10.17487/RFC5545, September 2009, RFC 5545, DOI 10.17487/RFC5545, September 2009,
<http://www.rfc-editor.org/info/rfc5545>. <https://www.rfc-editor.org/info/rfc5545>.
[RFC5988] Nottingham, M., "Web Linking", RFC 5988, [RFC5988] Nottingham, M., "Web Linking", RFC 5988,
DOI 10.17487/RFC5988, October 2010, DOI 10.17487/RFC5988, October 2010,
<http://www.rfc-editor.org/info/rfc5988>. <https://www.rfc-editor.org/info/rfc5988>.
[W3C.CR-skos-reference-20090317]
Bechhofer, S. and A. Miles, "SKOS Simple Knowledge
Organization System Reference", World Wide Web Consortium
CR CR-skos-reference-20090317, March 2009,
<http://www.w3.org/TR/2009/CR-skos-reference-20090317>.
[W3C.REC-xml-20060816] [W3C.REC-xml-20060816]
Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fourth F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fourth
Edition)", World Wide Web Consortium Recommendation REC- Edition)", World Wide Web Consortium Recommendation REC-
xml-20060816, August 2006, xml-20060816, August 2006,
<http://www.w3.org/TR/2006/REC-xml-20060816>. <http://www.w3.org/TR/2006/REC-xml-20060816>.
[W3C.WD-xptr-xpointer-20021219] [W3C.WD-xptr-xpointer-20021219]
DeRose, S., Daniel, R., and E. Maler, "XPointer xpointer() DeRose, S., Daniel, R., and E. Maler, "XPointer xpointer()
Scheme", World Wide Web Consortium WD WD-xptr-xpointer- Scheme", World Wide Web Consortium WD WD-xptr-xpointer-
20021219, December 2002, 20021219, December 2002,
<http://www.w3.org/TR/2002/WD-xptr-xpointer-20021219>. <http://www.w3.org/TR/2002/WD-xptr-xpointer-20021219>.
Appendix A. Change log
V04: 2014-11-18 MD
o Add 5545 registrations.
o Drop Q-name in favor of URI.
o Change REFID value type to text.
o Add STRUCTURED-CATEGORY property.
o Add STRUCTURED-CATEGORY relationship to RELATED-TO.
V03: 2014-09-21 MD
o Added Q-name specification.
o Change RELATED-ID to REFID and change its value type to Q-name.
o Add REFID relationship to RELATED-TO.
V02: 2013-11-22 MD
o Added more description to GAP
V01: 2013-09-26 MD
o Removed "Improved" from title
o Fixed typos and examples
o Removed gap param from link
2013-06-02 MD Initial version
Author's Address Author's Address
Michael Douglass Michael Douglass
Spherical Cow Group Spherical Cow Group
226 3rd Street 226 3rd Street
Troy, NY 12180 Troy, NY 12180
USA USA
Email: mdouglass@sphericalcowgroup.com Email: mdouglass@sphericalcowgroup.com
URI: http://sphericalcowgroup.com URI: http://sphericalcowgroup.com
 End of changes. 32 change blocks. 
100 lines changed or deleted 72 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/