Re: [urn] Transition of 2141bis and 3406bis

[Peter Saint-Andre <[e-mail]>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Juha, my apologies for the delayed reply. One question inline about
query components.

On 12/21/12 12:10 AM, Juha Hakala wrote:
> 
> On 27.11.2012 22:37, Andrew Newton wrote:

<snip/>

>> It should be noted that these new documents are not the final
>> output of this working group but are simply a new basis for the
>> development of the milestones we must achieve, and they will be
>> based on consensus within this working group and the IETF in
>> accordance with IETF practices.
> 
> I hope the WG will succeed in this task, and wish it would have
> been possible to find consensus on how to use fragment and query.
> Since this did not seem likely, the Finnish ISO TC 46 shadow
> committee decided in its meeting 2012-12-10 to start the
> development of a national URN syntax standard. The standard will be
> bilingual (English and Finnish) and it will be based on the latest
> 2141bis version Alfred Hoenes wrote. Our intention is to keep the
> document downward compatible with whatever the URNbis WG will come
> up with.

Could you explain a bit more clearly the intended usage of query
components in URNs? As far as I have been able to determine, no one
has proposed to include query components in URNs themselves (e.g.,
"urn:isbn:978-951-1-25645-8?param=value"), only in URIs (mostly HTTP
URIs) that encapsulate such a URN for resolution purposes and then
append a query component to the end of the URI (say,
"http://resolver.example.com/urn:isbn:978-951-1-25645-8?param=value").
Does the Finnish ISO TC 46 shadow committee plan to proceed along the
URI path, or do they plan to include query components in URNs themselves?

Could you also explain (perhaps in a separate thread) the intended use
of the fragment identifier, as well as any other discrepancies between
the shadow committee's approach and 2141bis and 3406bis as they stand
today?

Many thanks,

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRJazyAAoJEOoGpJErxa2p+9IQAKeLUaovxAC6J1kmYFO6wYOi
MMM+3ywObqB64iz2AgHVt0hq2fWO+B1GvlDWmEAiQZcQkDHICYkqSawyJrYqKU8O
ljP7+19VlqbfvzOFuNJvo6FbnrVBTo3bcT0yKqqTt8EpI0qD7DE7yo8D1FfbOj1V
27Q5ydkK5tl2dagzkNYlgFj2cNRwluFCZvtSd0RZI/MrOd0IxD5GXZ1g4gOjRi9Q
ZQkvQ0BliFaxbPGmJjtfIV9e2KotpPfRBjSf8Q+p9ETTt/3VMEHaa+VubMQeYy9N
df/pJtAZMQAzrl+6zVgY3CR+LTUIX8zdUJ6DMs8wBSKhH3CgUz1rppKB7cAUulsB
ZXPvl1oTstyYZHrbkicKed5MUA0yw5MZMYkRygcCWZx8wejM5RfXjVRMKHdDiTPO
kH3s53hpk8+yyvfMkzWI8KIjErzW+ZJfW4Jq4SVgDcn/jLf0pB7Q3bAQCW4nw7J4
oSTsFyPB+BJYy3cW+CSbbW9DzgmUyUtJcsEs/I9WyWr3ILNFiN+/1dC3pvS1A+N9
GCGZ7iDm7E2r8uLbiEkmjiEvOP5ngbfmIdfEn/Z4anmytWMFv4+DJ5d+jTuEeHbV
jyHc40eFGEGfTKMVJHFU8koZ4Lc/tf1figiWvvMmnIVECT3ttJke+kIf4vo8wW/+
dfZU65edw2k1eBmeKkwA
=5mpd
-----END PGP SIGNATURE-----