Hi Bill,
FYI, This isn't very important but I thought I'd mention it:
I was staring at our gnucash URL's: e.g.
<A HREF="gnc-register:guid=bba3ebdb3d43c5d097c737426e7c5c78">Income</A>
and realized that there's an internet draft for this stuff (excerpt
below). If we follow the draft, a compliant format would be:
<A HREF="uuid:bba3ebdb-3d43-c5d0-97c7-37426e7c5c78;display=gnc-register">Income</A>
--linas
================================================================
http://globecom.net/ietf/draft/draft-kindel-uuid-uri-00.html
To enable the use of UUIDs as URI's within Internet documents this
memo defines a simple UUID URI scheme. Using the scheme described in
this memo, the above UUID would be represented as:
uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
The basic structure of a UUID URI is:
uuid:<uuid>;<qualifiers>
where <uuid> is a string representation of a UUID, which is
documented
in [UUID]. The optional set of qualifiers are specified as name/value
pairs separated by semi-colons. There are currently no qualifiers
defined. However, UUID URI parsers should be written to gracefully
ignore any characters that appear after the last character of the
UUID
(UUID strings are always 36 characters long).
UUIDs must be generated using well known algorithms.
6. BNF FOR THE UUID URI
A uuid URI begins with the scheme prefix "uuid" and is defined by the
following grammar:
uuid-uri = "uuid:" uuid [qualifiers]
uuid = 8hex "-" 4hex "-" 4hex "-" 4hex "-" 12hex
qualifiers = [";" name = value]*
hex = "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" |
"8" | "9" | "a" | "b" | "c" | "d" | "e" | "f" |
"A" | "B" | "C" | "D" | "E" | "F"
PGP signature
