OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [xri] Comments on xri-syntax-2.0-wd-05


Nat-
 
Publishing this in a non-normative doc sounds like a fine idea - I'm not even sure the TC would do it. No matter what, I think we need to focus on that *after* the phone call on the 14th.
 
In anticipation of this, would someone who is familiar with python like to take that code and review it with a fine tooth comb?  THANKS (code linked from http://www.wachob.com/xriescape/)
 
    -Gabe


From: Sakimura, Nat [mailto:n-sakimura@nri.co.jp]
Sent: Thursday, March 03, 2005 3:26 PM
To: Wachob, Gabe; xri@lists.oasis-open.org
Subject: RE: [xri] Comments on xri-syntax-2.0-wd-05

Let's put all those in the INTRO document, which we can rev. freely.
 
Nat


From: Wachob, Gabe [mailto:gwachob@visa.com]
Sent: Friday, March 04, 2005 1:41 AM
To: Sakimura, Nat; xri@lists.oasis-open.org
Subject: RE: [xri] Comments on xri-syntax-2.0-wd-05

My concern with including code is that I'm not 100% certain it conforms to the specification, and ensuring that is does would slow things down. In fact, I have made certain design decisions (such as ignoring the font-metadata normalization step) that others may not want to ignore, so I don't know if we want to suggest that the code I have is appropriate for all applications.  
 
I have mentioned before that someone (perhaps the TC) should maintain a "test suite" of XRI and how they are parsed and converted (into IRI and URI). Perhaps this code could be published along with that effort?
 
    -Gabe


From: Sakimura, Nat [mailto:n-sakimura@nri.co.jp]
Sent: Thursday, March 03, 2005 7:31 AM
To: xri@lists.oasis-open.org
Subject: [xri] Comments on xri-syntax-2.0-wd-05

Congratulations. From may point of view, this is pretty much baked.
 
Now, couple of points:
 
(1) Color coding of exhibit is very useful, but is not very accessible to those with
     color related sight problems.
     It is better having different borders of the exhibit in addition to the color.
 
(2) Is it possible to have something like Gabe's escaping tool code as an appendix?
     That's going to be extremely useful for the readers. Just having the code published 
     as an informative document and reference that would be a second best option. 
 
Cheers,
 
Nat


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]