[core] Review of draft-ietf-core-coral-03

[Jim Schaad <[e-mail]>]

Section 2.3 – Suggested text change s/are in contrast denoted/are, in contrast, denoted/  I keep thinking that by contrast should be used, but I keep going back and forth on that so I would leave that along.  If you go that it would be /types, by contrast, are denoted/

 

Section 2.3 – s/collisions when from different/collisions from/

 

Section 2.3 – The CBOR WG is defining two new tags for Date and TimeOfDay.  Should these be added as new literal values?

 

Section 2.3 – s/is neither identified by/is identified by neither/

 

Section 2.6 – Step 5 – Can the request method be a FETCH as well as a GET? 

 

Section 4.1.4 – I do not believe that expanding the MEDIAL character set is really a good idea.  Consider the following where one of the line uses HYPEN-MINUS and the other line uses ARMENIAN HYPEN.  I cannot see a difference if I am reading this.
#using AB-CD = IRI1
#using AB֊CD = IRI2

 

Section 4.1.5.3 – There is a difference between the text and the ABNF for hexadecimal.  One of them only has the lowercase character and the other has both upper- and lowercase ‘x’.

 

Section 5.2 – I am trying to figure out if not returning a CoRAL document is considered to be reasonable or not.  Does the phrase “processing result” indicate an absent content?

 

Section 5.2.1 – If I return a link to the new document created in a CoRAL document, should I also return the location options or should they be omitted?

 

Section 6.1.3 – I am wondering if an application might also require that the links and forms in a document be encoded in a specific order?

 

I skimmed the end of the document so I may do another pass on that section later.

 

Jim