RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Reported (1)

RFC 6415, "Web Host Metadata", October 2011

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 4811
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Dale R. Worley
Date Reported: 2016-09-26

Section 3.1.1 says: 

   The XRD "Link" element, when used with the "href" attribute, conveys
   a link relation between the host described by the document and a
   common target URI.

It should say:

   The XRD "Link" element, when used with the "href" attribute, conveys
   a link relation between the host described by the document and a
   common target URI-reference.

Notes:

The erratum changes the text to allow the value of the href attribute to be a URI-reference, that is, either a URI or a relative-reference.

It appears that the new text is what has always been intended, because RFC 6415 is taken from Extensible Resource Descriptor (XRD) Version 1.0
(http://docs.oasis-open.org/xri/xrd/v1.0/xrd-1.0.html) sections 2.6 and 1.5.2, which specifies the value to be an "anyURI" in the XML schema datatypes, which includes relative URIs. "URI-reference" in RFC 3986 is equivalent to "anyURI" in XML schema datatypes.

This erratum now matters, because draft-ietf-netconf-restconf makes significant use of href values that are relative URLs. Also, see the discussion at https://www.ietf.org/mail-archive/web/netconf/current/msg11768.html

Status: Held for Document Update (1)

RFC 6415, "Web Host Metadata", October 2011

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 3118
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Christian Weiske
Date Reported: 2012-02-09
Held for Document Update by: Peter Saint-Andre
Date Held: 2012-02-27

Section Appendix A. says: 

      <Subject>http://blog.example.com/article/id/314</Subject>
      <Expires>2010-01-30T09:30:00Z</Expires>

It should say:

      <Expires>2010-01-30T09:30:00Z</Expires>
      <Subject>http://blog.example.com/article/id/314</Subject>

Notes:

The XML example in Appendix A. has the Subject before the Expires tag, which is wrong.

XRD 1.0 defines[1] the <XRD> element as a "sequence" with <Expires> first, <Subject> second. A sequence is defined[2] as "Sequence (the element information items match the particles in sequential order);".

PSA: Because this is a minor problem with a non-normative example, processing as "Hold For Document Update". -- Peter Saint-Andre

[1] http://docs.oasis-open.org/xri/xrd/v1.0/xrd-1.0.html#element.xrd
[2] http://www.w3.org/TR/xmlschema-1/#Model_Group

Report New Errata



Advanced Search