RE: [xri-editors] Reviewing RC1b

["Wachob, Gabe" <gwachob@visa.com>]

Drummond-

	Here's my feedback. I thought I'd do it in an email separate because it easier to deal with I think this way. 

	* The definitions for normal and canonical form are plain confusing. E.g. in canonical form - "in order to satisfy identifier equivalence requirements".. I think the word "requirements" is wrong here (they are equivalence rules), and also this seems really non-specific. What does "satisfy" mean, for example? And its not a "format" - its a state of an identifier. Its probably better to state "An identifier is said to be in canonical form when X is true. " (where X is something like "doesn't contain $! or ! cross-references, etc"). Is there separate canonical forms for URI and XRI forms? In resolution, we need to deal with URI Canonical form. See bullet point below also on a change to resolution section. 
	
	* At least one reference (sectoin 2.1.2 - maybe more?) within the document are broken due (I'm guessing) to removing sections. 

	* section 2.4.1 - "meets these rules" - this section describes a bunch of equivalence rules (X and Y are equivalent). It doesn't make any sense to say that an identifier "meets these rules". We still haven't defined the canonical form, and we need to, for the purposes of resolution. For example, we need to say "the canonical form is the form of an XRI with all of the ($! cross-references removed, optional leading '.'s inserted, etc". 

	* The use of example-community.org is better than xri.org, but how about using oasis-open.org since we know that example-community.org could be registered (perhaps maliciously) and we'd then have the problems we currently have with xri.org.. 

	* The example that nat fixed (dsr15) need to be fixed in the rest of 3.2.5 (ie adding the . in the example URIs in the text before the sample HTTP request and responses). Need to check the rest of 3.2.5 
	
	* Need to mention in the resolution section that the "canonical form" is being resolved. Probably can do this in the bullet list at 3.1.1 - change "URI normal form" to "Canonical form". Again, though, its not clear to me that "canonical form" is defined as the "URI normal form with all of the $!, ! cross references removed, and the segment-leading "."'s inserted (where appropriate)" as I think it should be defined.

	Otherwise, consider changes accepted.

	-Gabe

	

> -----Original Message-----
> From: Drummond Reed [mailto:drummond.reed@onename.com]
> Sent: Monday, November 10, 2003 1:00 AM
> To: xri-editors@lists.oasis-open.org
> Subject: [xri-editors] Reviewing RC1b
> 
> 
> Editors,
>  
> I just uploaded RC1b to the Editor's SC for review by the 
> editors before
> posting as RC2 to the main TC (ideally RC2 is final final before the
> vote, so I want us all to review it before posting). For ease 
> of review,
> EVERY change (edit or addition) is commented, so you can just open the
> comment window and click each comment to review.
>  
> Here are the main thrusts:
>  
> 1) Eagle-eye Nat did a great job of: a) providing the example of ASCII
> char sequences that are non-legal UTF-8, and b) proofing the spec (he
> caught the missing dots in some of the resolution examples).
>  
> 2) In discussing the $! metadata issue with me on Friday, Gabe brought
> up the issue of "canonicalization" of XRIs, and we both realized that
> this was a better way to deal with the whole issue of what we had been
> calling "optional syntax". So I added a definition of canonical form,
> changed the title of that section with 2.4, and reordered it to come
> first.
>  
> 3) After Gabe's and my conversation about $!, I added a section called
> "Encoding Presentation Metadata" that is patterned after the "Encoding
> Non-UTF-8 Language and Font Metadata" section. Note that I added this
> section BEFORE the "Transforming XRIs into IRIs and URIs" section
> because it deals with a higher-level concept, namely "Transforming
> Display Strings into XRIs". In other words, the purpose of $! is
> capturing display metadata that otherwise may be lost when 
> converting a
> display string into a valid XRI in escaped normal form. This metadata,
> which can address difficult issues we've been discussing like spaces,
> case, and punctuation, can be lost DURING the transformation into
> escaped normal form depending on an authority's XRI 
> normalization rules
> (which might, for example, disallow even %20 encoded spaces or capital
> letter). So my reasoning was that if this data needed to be 
> retained for
> later display, it needed to be captured into a $! cross-reference at
> that juncture.
>  
> (Note to Gabe: I realized I couldn't add $f and $l to the $! space
> because they ARE significant in comparision, while $! metadata is not.
> That's another reason I added this section prior to the "Transforming
> XRIs into IRIs and URIs" section.)
>  
> Please review all these edits, especially this new section, 
> and post any
> feedback. To my knowledge, this is the only remaining ISSUE in RC1b.
> With Nat's outstanding tasks done, everything else is 
> strictly a matter
> of reviewing new or added wording. So if we can close this 
> issue by COB
> TOMORROW, MONDAY, then I will post RC2 (incorporating any 
> final feedback
> on these edits and any other feedback) Tuesday morning.
>  
> Note that I will be offline from about 9am - 4pm tomorrow, but during
> that time you can get me on my cell, 206.618.8530.
>  
> =Drummond 
> 
> To unsubscribe from this mailing list (and be removed from 
> the roster of the OASIS TC), go to 
http://www.oasis-open.org/apps/org/workgroup/xri-editors/members/leave_workgroup.php.