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


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

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

Subject: Re: [regrep] Issue with UUID's for Core Components and BIE's

David RR Webber wrote:

>I hope this is the last and final time we have to have this discussion
>around erroneous use of UUID values as external linkage identifiers
>to registry content - they are for INTERNAL use only - and should
>be used for such programmatic pointer uses only within the API
>to registry.   
I respectfully disagree. The UUID based URN (urn:uuid:....) should be 
used to
uniquely reference an object internally or externally. I agree that for 
consumption you may want some ExternalIdentifier such as a human 
friendly URN.
But strictly for reference purposes (internal or external to registry) I 
suggest using UUID based URNs.

>I understand the tempatation to make your Java code
>easier to write by burying all these UUIDs into the access method
>to the registry - as a quick kludge - but you have to remember the
>central tenet of computer software - its supposed to make work
>easier for human operators - not harder!   Not to mention the
>ludicrous overhead associated with a 128 byte boat anchor to
>what is often less than 30 bytes of information....
Oops, I think you meant to say a "16 byte boat anchor" not a "128 byte 
boat anchor".
Which is definitely less than "30 bytes of information".

To be clear... A UUID is 16 bytes not 128 bytes.


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