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:]
Sent: Thursday, March 03, 2005 7:31 AM
To:
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
