Eclipse Community Forums - RDF feed
https://www.eclipse.org/forums/
Eclipse Community Forumsuuid and oid
https://www.eclipse.org/forums/index.php/mv/msg/12837/40271/#msg_40271
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]]>Jesse Pangburn2008-01-16T19:21:38-00:00Re: uuid and oid
https://www.eclipse.org/forums/index.php/mv/msg/12837/40336/#msg_40336
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
>
>
>]]>No real name2008-01-22T22:34:20-00:00Re: uuid and oid
https://www.eclipse.org/forums/index.php/mv/msg/12837/584434/#msg_584434
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
>
>
>]]>No real name2008-01-22T22:34:20-00:00Re: uuid and oid
https://www.eclipse.org/forums/index.php/mv/msg/12837/40367/#msg_40367
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
>>
>>
>>]]>Jesse Pangburn2008-01-23T02:13:06-00:00Re: uuid and oid
https://www.eclipse.org/forums/index.php/mv/msg/12837/584444/#msg_584444
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
>>
>>
>>]]>Jesse Pangburn2008-01-23T02:13:06-00:00Re: uuid and oid
https://www.eclipse.org/forums/index.php/mv/msg/12837/584456/#msg_584456
> 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
>>>
>>>
>>>
>
>]]>Matthew Davis2008-01-23T17:14:43-00:00Re: uuid and oid
https://www.eclipse.org/forums/index.php/mv/msg/12837/40397/#msg_40397
> 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
>>>
>>>
>>>
>
>]]>Matthew Davis2008-01-23T17:14:43-00:00Re: uuid and oid
https://www.eclipse.org/forums/index.php/mv/msg/12837/584462/#msg_584462
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
>>>
>>>
>>>
>
>]]>No real name2008-01-23T22:30:35-00:00Re: uuid and oid
https://www.eclipse.org/forums/index.php/mv/msg/12837/40429/#msg_40429
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
>>>
>>>
>>>
>
>]]>No real name2008-01-23T22:30:35-00:00