Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » OHF » uuid and oid
uuid and oid [message #40271] Wed, 16 January 2008 19:21 Go to next message
Jesse Pangburn is currently offline Jesse Pangburn
Messages: 166
Registered: July 2009
Senior Member
This is kind of a noob question, but can anyone explain the purpose of
uuid and oid in XDS?

I see that when you submit a document you generate a unique oid value to
submit as the document's oid. When the Provide and Register transaction
finishes, it returns a uuid value. Why have two unique id values for a
given document?

Using the bridge, when you want to provide a parent document id to
deprecate you specify the uuid. Maybe this has something to do with why
there needs to be two unique ids associated with one document?

thanks,
Jesse
Re: uuid and oid [message #40336 is a reply to message #40271] Tue, 22 January 2008 22:34 Go to previous messageGo to next message
No real name is currently offline No real name
Messages: 292
Registered: July 2009
Senior Member
Hi Jesse,

Some good questions. This is a combination of factors ... none of which
are particularly satisfying. the UUIDs come out of the choice to use
ebXML. The ebXML structures for document entries, folders and submission
sets all require the use of an 'id'. This 'id' is used in ebXML to
reference these objects internally with in the registry. Thus a UUID in
XDS can be described as an id that is unique with-in the registry. But
this is not necessarily useful or meaningful out side of the registry.
That is why they have the unique ids. These are intended to be globally
unique and are to mean something outside the bounds of the registry.

Hope this helps,
- Sarah




Jesse Pangburn wrote:
> This is kind of a noob question, but can anyone explain the purpose of
> uuid and oid in XDS?
>
> I see that when you submit a document you generate a unique oid value to
> submit as the document's oid. When the Provide and Register transaction
> finishes, it returns a uuid value. Why have two unique id values for a
> given document?
>
> Using the bridge, when you want to provide a parent document id to
> deprecate you specify the uuid. Maybe this has something to do with why
> there needs to be two unique ids associated with one document?
>
> thanks,
> Jesse
>
>
>
Re: uuid and oid [message #40367 is a reply to message #40336] Wed, 23 January 2008 02:13 Go to previous messageGo to next message
Jesse Pangburn is currently offline Jesse Pangburn
Messages: 166
Registered: July 2009
Senior Member
Hi Sarah,
Thanks as always for your help.

As UUID stands for "universally unique identifier", it would seem to me to
be sufficient for uniquely identifying a document inside and out of the
registry. I saw (after sending an OID incorrectly) that the registry does
require UUIDs, as you said to reference stuff internally. So then I
wondered why bother with OIDs since we're already making a unique ID for a
doc in a registry.

Maybe someone thought since UUIDs are only guaranteed unique if properly
generated they should use OIDs. Oh well, I guess as you also said, it's
not "particularly satisfying". Probably one of the initiators had some
odd reason they found compelling...

thanks,
Jesse

Sarah Knoop wrote:

> Hi Jesse,

> Some good questions. This is a combination of factors ... none of which
> are particularly satisfying. the UUIDs come out of the choice to use
> ebXML. The ebXML structures for document entries, folders and submission
> sets all require the use of an 'id'. This 'id' is used in ebXML to
> reference these objects internally with in the registry. Thus a UUID in
> XDS can be described as an id that is unique with-in the registry. But
> this is not necessarily useful or meaningful out side of the registry.
> That is why they have the unique ids. These are intended to be globally
> unique and are to mean something outside the bounds of the registry.

> Hope this helps,
> - Sarah




> Jesse Pangburn wrote:
>> This is kind of a noob question, but can anyone explain the purpose of
>> uuid and oid in XDS?
>>
>> I see that when you submit a document you generate a unique oid value to
>> submit as the document's oid. When the Provide and Register transaction
>> finishes, it returns a uuid value. Why have two unique id values for a
>> given document?
>>
>> Using the bridge, when you want to provide a parent document id to
>> deprecate you specify the uuid. Maybe this has something to do with why
>> there needs to be two unique ids associated with one document?
>>
>> thanks,
>> Jesse
>>
>>
>>
Re: uuid and oid [message #40397 is a reply to message #40367] Wed, 23 January 2008 17:14 Go to previous messageGo to next message
Matthew Davis
Messages: 269
Registered: July 2009
Senior Member
> As UUID stands for "universally unique identifier", it would seem to me
> to be sufficient for uniquely identifying a document inside and out of
> the registry. I saw (after sending an OID incorrectly) that the
> registry does require UUIDs, as you said to reference stuff internally.
> So then I wondered why bother with OIDs since we're already making a
> unique ID for a doc in a registry.

haha, I said the same thing when it was explained to me, too :)

Ah the world we live in.

-Matt

> Sarah Knoop wrote:
>
>> Hi Jesse,
>
>> Some good questions. This is a combination of factors ... none of
>> which are particularly satisfying. the UUIDs come out of the choice to
>> use ebXML. The ebXML structures for document entries, folders and
>> submission sets all require the use of an 'id'. This 'id' is used in
>> ebXML to reference these objects internally with in the registry. Thus
>> a UUID in XDS can be described as an id that is unique with-in the
>> registry. But this is not necessarily useful or meaningful out side of
>> the registry. That is why they have the unique ids. These are intended
>> to be globally unique and are to mean something outside the bounds of
>> the registry.
>
>> Hope this helps,
>> - Sarah
>
>
>
>
>> Jesse Pangburn wrote:
>>> This is kind of a noob question, but can anyone explain the purpose
>>> of uuid and oid in XDS?
>>>
>>> I see that when you submit a document you generate a unique oid value
>>> to submit as the document's oid. When the Provide and Register
>>> transaction finishes, it returns a uuid value. Why have two unique
>>> id values for a given document?
>>>
>>> Using the bridge, when you want to provide a parent document id to
>>> deprecate you specify the uuid. Maybe this has something to do with
>>> why there needs to be two unique ids associated with one document?
>>>
>>> thanks,
>>> Jesse
>>>
>>>
>>>
>
>
Re: uuid and oid [message #40429 is a reply to message #40367] Wed, 23 January 2008 22:30 Go to previous message
No real name is currently offline No real name
Messages: 292
Registered: July 2009
Senior Member
I understand ... and have no further justification to offer other than
HL7 loves OIDs and maybe they are someone else's favorites too:-)

- Sarah

Jesse Pangburn wrote:
> Hi Sarah,
> Thanks as always for your help.
>
> As UUID stands for "universally unique identifier", it would seem to me
> to be sufficient for uniquely identifying a document inside and out of
> the registry. I saw (after sending an OID incorrectly) that the
> registry does require UUIDs, as you said to reference stuff internally.
> So then I wondered why bother with OIDs since we're already making a
> unique ID for a doc in a registry.
>
> Maybe someone thought since UUIDs are only guaranteed unique if properly
> generated they should use OIDs. Oh well, I guess as you also said, it's
> not "particularly satisfying". Probably one of the initiators had some
> odd reason they found compelling...
>
> thanks,
> Jesse
>
> Sarah Knoop wrote:
>
>> Hi Jesse,
>
>
>> Some good questions. This is a combination of factors ... none of
>> which are particularly satisfying. the UUIDs come out of the choice to
>> use ebXML. The ebXML structures for document entries, folders and
>> submission sets all require the use of an 'id'. This 'id' is used in
>> ebXML to reference these objects internally with in the registry. Thus
>> a UUID in XDS can be described as an id that is unique with-in the
>> registry. But this is not necessarily useful or meaningful out side of
>> the registry. That is why they have the unique ids. These are intended
>> to be globally unique and are to mean something outside the bounds of
>> the registry.
>
>
>> Hope this helps,
>> - Sarah
>
>
>
>
>
>> Jesse Pangburn wrote:
>>
>>> This is kind of a noob question, but can anyone explain the purpose
>>> of uuid and oid in XDS?
>>>
>>> I see that when you submit a document you generate a unique oid value
>>> to submit as the document's oid. When the Provide and Register
>>> transaction finishes, it returns a uuid value. Why have two unique
>>> id values for a given document?
>>>
>>> Using the bridge, when you want to provide a parent document id to
>>> deprecate you specify the uuid. Maybe this has something to do with
>>> why there needs to be two unique ids associated with one document?
>>>
>>> thanks,
>>> Jesse
>>>
>>>
>>>
>
>
Re: uuid and oid [message #584434 is a reply to message #40271] Tue, 22 January 2008 22:34 Go to previous message
No real name is currently offline No real name
Messages: 292
Registered: July 2009
Senior Member
Hi Jesse,

Some good questions. This is a combination of factors ... none of which
are particularly satisfying. the UUIDs come out of the choice to use
ebXML. The ebXML structures for document entries, folders and submission
sets all require the use of an 'id'. This 'id' is used in ebXML to
reference these objects internally with in the registry. Thus a UUID in
XDS can be described as an id that is unique with-in the registry. But
this is not necessarily useful or meaningful out side of the registry.
That is why they have the unique ids. These are intended to be globally
unique and are to mean something outside the bounds of the registry.

Hope this helps,
- Sarah




Jesse Pangburn wrote:
> This is kind of a noob question, but can anyone explain the purpose of
> uuid and oid in XDS?
>
> I see that when you submit a document you generate a unique oid value to
> submit as the document's oid. When the Provide and Register transaction
> finishes, it returns a uuid value. Why have two unique id values for a
> given document?
>
> Using the bridge, when you want to provide a parent document id to
> deprecate you specify the uuid. Maybe this has something to do with why
> there needs to be two unique ids associated with one document?
>
> thanks,
> Jesse
>
>
>
Re: uuid and oid [message #584444 is a reply to message #40336] Wed, 23 January 2008 02:13 Go to previous message
Jesse Pangburn is currently offline Jesse Pangburn
Messages: 166
Registered: July 2009
Senior Member
Hi Sarah,
Thanks as always for your help.

As UUID stands for "universally unique identifier", it would seem to me to
be sufficient for uniquely identifying a document inside and out of the
registry. I saw (after sending an OID incorrectly) that the registry does
require UUIDs, as you said to reference stuff internally. So then I
wondered why bother with OIDs since we're already making a unique ID for a
doc in a registry.

Maybe someone thought since UUIDs are only guaranteed unique if properly
generated they should use OIDs. Oh well, I guess as you also said, it's
not "particularly satisfying". Probably one of the initiators had some
odd reason they found compelling...

thanks,
Jesse

Sarah Knoop wrote:

> Hi Jesse,

> Some good questions. This is a combination of factors ... none of which
> are particularly satisfying. the UUIDs come out of the choice to use
> ebXML. The ebXML structures for document entries, folders and submission
> sets all require the use of an 'id'. This 'id' is used in ebXML to
> reference these objects internally with in the registry. Thus a UUID in
> XDS can be described as an id that is unique with-in the registry. But
> this is not necessarily useful or meaningful out side of the registry.
> That is why they have the unique ids. These are intended to be globally
> unique and are to mean something outside the bounds of the registry.

> Hope this helps,
> - Sarah




> Jesse Pangburn wrote:
>> This is kind of a noob question, but can anyone explain the purpose of
>> uuid and oid in XDS?
>>
>> I see that when you submit a document you generate a unique oid value to
>> submit as the document's oid. When the Provide and Register transaction
>> finishes, it returns a uuid value. Why have two unique id values for a
>> given document?
>>
>> Using the bridge, when you want to provide a parent document id to
>> deprecate you specify the uuid. Maybe this has something to do with why
>> there needs to be two unique ids associated with one document?
>>
>> thanks,
>> Jesse
>>
>>
>>
Re: uuid and oid [message #584456 is a reply to message #40367] Wed, 23 January 2008 17:14 Go to previous message
Matthew Davis
Messages: 269
Registered: July 2009
Senior Member
> As UUID stands for "universally unique identifier", it would seem to me
> to be sufficient for uniquely identifying a document inside and out of
> the registry. I saw (after sending an OID incorrectly) that the
> registry does require UUIDs, as you said to reference stuff internally.
> So then I wondered why bother with OIDs since we're already making a
> unique ID for a doc in a registry.

haha, I said the same thing when it was explained to me, too :)

Ah the world we live in.

-Matt

> Sarah Knoop wrote:
>
>> Hi Jesse,
>
>> Some good questions. This is a combination of factors ... none of
>> which are particularly satisfying. the UUIDs come out of the choice to
>> use ebXML. The ebXML structures for document entries, folders and
>> submission sets all require the use of an 'id'. This 'id' is used in
>> ebXML to reference these objects internally with in the registry. Thus
>> a UUID in XDS can be described as an id that is unique with-in the
>> registry. But this is not necessarily useful or meaningful out side of
>> the registry. That is why they have the unique ids. These are intended
>> to be globally unique and are to mean something outside the bounds of
>> the registry.
>
>> Hope this helps,
>> - Sarah
>
>
>
>
>> Jesse Pangburn wrote:
>>> This is kind of a noob question, but can anyone explain the purpose
>>> of uuid and oid in XDS?
>>>
>>> I see that when you submit a document you generate a unique oid value
>>> to submit as the document's oid. When the Provide and Register
>>> transaction finishes, it returns a uuid value. Why have two unique
>>> id values for a given document?
>>>
>>> Using the bridge, when you want to provide a parent document id to
>>> deprecate you specify the uuid. Maybe this has something to do with
>>> why there needs to be two unique ids associated with one document?
>>>
>>> thanks,
>>> Jesse
>>>
>>>
>>>
>
>
Re: uuid and oid [message #584462 is a reply to message #40367] Wed, 23 January 2008 22:30 Go to previous message
No real name is currently offline No real name
Messages: 292
Registered: July 2009
Senior Member
I understand ... and have no further justification to offer other than
HL7 loves OIDs and maybe they are someone else's favorites too:-)

- Sarah

Jesse Pangburn wrote:
> Hi Sarah,
> Thanks as always for your help.
>
> As UUID stands for "universally unique identifier", it would seem to me
> to be sufficient for uniquely identifying a document inside and out of
> the registry. I saw (after sending an OID incorrectly) that the
> registry does require UUIDs, as you said to reference stuff internally.
> So then I wondered why bother with OIDs since we're already making a
> unique ID for a doc in a registry.
>
> Maybe someone thought since UUIDs are only guaranteed unique if properly
> generated they should use OIDs. Oh well, I guess as you also said, it's
> not "particularly satisfying". Probably one of the initiators had some
> odd reason they found compelling...
>
> thanks,
> Jesse
>
> Sarah Knoop wrote:
>
>> Hi Jesse,
>
>
>> Some good questions. This is a combination of factors ... none of
>> which are particularly satisfying. the UUIDs come out of the choice to
>> use ebXML. The ebXML structures for document entries, folders and
>> submission sets all require the use of an 'id'. This 'id' is used in
>> ebXML to reference these objects internally with in the registry. Thus
>> a UUID in XDS can be described as an id that is unique with-in the
>> registry. But this is not necessarily useful or meaningful out side of
>> the registry. That is why they have the unique ids. These are intended
>> to be globally unique and are to mean something outside the bounds of
>> the registry.
>
>
>> Hope this helps,
>> - Sarah
>
>
>
>
>
>> Jesse Pangburn wrote:
>>
>>> This is kind of a noob question, but can anyone explain the purpose
>>> of uuid and oid in XDS?
>>>
>>> I see that when you submit a document you generate a unique oid value
>>> to submit as the document's oid. When the Provide and Register
>>> transaction finishes, it returns a uuid value. Why have two unique
>>> id values for a given document?
>>>
>>> Using the bridge, when you want to provide a parent document id to
>>> deprecate you specify the uuid. Maybe this has something to do with
>>> why there needs to be two unique ids associated with one document?
>>>
>>> thanks,
>>> Jesse
>>>
>>>
>>>
>
>
Previous Topic:Quick Update - Connectathon Coming Soon!
Next Topic:PDQ limit
Goto Forum:
  


Current Time: Fri Oct 24 11:38:50 GMT 2014

Powered by FUDForum. Page generated in 0.04137 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software