Unique OAF Implementation ID's

[ERDI Gergo <cactus cactus rulez org>]

Hi,

I've talked with Michael about OAF UIID's, and I realized that
	a, what OAF UIID's are about is not clear, and
	b, the current cryptic hex numbers scheme is not nice.
Point a, is that it's not clear wether the IID needs to be unique for
applications, or for specific versions (i.e. is it `implementation' as in
`this is the Helix implementation of Wombat' or is it `implementation' as
in `this is the 0.6 implementation of Helix Wombat'?). It seems to me the
former is correct, since I have yet to see a package changing its UIID
with a new release. If I'm not right on this one, please discard point b,.

Point b, is that if the purpose of the UIID is to identify a
specific program that implements the given interfaces, why not use
something human-readable, e.g. the vendor's and the product's name?
So, my proposal is, something like
OAFIID:evolution:addressbook-server:helixcode
instead of the current
OAFIID:evolution:addressbook-server:0fbc844d-c721-4615-98d0-d67eacf42d80

-- 
   .--= ULLA! =----------------------------.  finger cactus@cactus.rulez.org
   \      http://cactus.rulez.org           \   for PGP public key
    `----------= cactus@cactus.rulez.org =--'
Két pont között a legrövidebb út építés alatt áll.