|
|
|
Andrew Grimshaw: 05/03/2006 12:22 PM EDT
|
| |
Comment: |
This is resolved by a combination of the unambigious web service endpoint proposed profile and the proposed web service endpoint address identifier
profile.
|
| |
Action: |
Update
|
|
|
Andrew Grimshaw: 05/03/2006 12:22 PM EDT
|
| |
Action: |
Update
artifact_status changed from Open to Closed
close_date changed from - to 2006-05-03 12:22:01
|
|
|
Mark Morgan: 04/05/2006 3:56 PM EDT
|
| |
Action: |
Update
artifact_status changed from Closed to Open
|
|
|
Mark Morgan: 04/05/2006 3:49 PM EDT
|
| |
Action: |
Update
artifact_status changed from Open to Closed
close_date changed from - to 2006-04-05 15:49:56
|
|
|
Mark Morgan: 04/05/2006 3:48 PM EDT
|
| |
Comment: |
Also note, you cannot use the address for the unique name as the address may change for a given resource over time (migration, etc.). Also, addresses
are in no way guaranteed to be unique.
|
| |
Action: |
Update
|
|
|
Andrew Grimshaw: 03/16/2006 10:20 AM EST
|
| |
Action: |
Update
assigned_to changed from 100 to 126
|
|
|
Andrew Grimshaw: 03/16/2006 10:18 AM EST
|
| |
Comment: |
This has been addressed by adding the following paragraph:
"The first property, global uniqueness in both space and time, can be achieved by a number of means. Implementers are free to choose any name
generation scheme that they wish to use provided the scheme generates unique names. Some options include various combinations and hashes of public
keys, MAC addresses, Generating IP address (not current web service endpoint address as that may change), timestamp, random number, etc. In
particular, the authors of this document recommend that name generators refer to RFC 4122 which motivates and describes the UUIDs or Universally
Unique IDs."
|
| |
Action: |
Update
|
|
|
|
