[ESW Wiki] Update of "its0505ReqUniqueID" by fsasaki

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "ESW Wiki" for change notification.

The following page has been changed by fsasaki:
http://esw.w3.org/topic/its0505ReqUniqueID


------------------------------------------------------------------------------
  '''[[YS-''' I think we want "unique within the document", which is much easier to insure. As far as making it unique outside of the document, I would guess one would simply need to add the document full path, relative path or filename, depending on the context of work (just like HTML anchors). Globably unique could be achieved also if needed, but I'm not sure if it would require a description of the document set. For example: MS GUIDs are "globally unique" and-I think-don't deal with document set(?) (but obviously it would be nicer to work with more human-readable IDs).''']]'''
  
  '''[[AZ-''' The best method is to attribute a unique ID to the document and then have unique ids within the document for individual text units. In this way the combination of unique document ID and unique text unit id are guaranteed to be totally unique. This is similar to Yves' suggestion, but separates out text unit ids from the document id. In order to achieve a unique document ID you take a CRC of the document and add to it the UTC current time in milliseconds as a modifier. All of this is covered by the proposed LISA OSCAR xml:tm specification (http://www.xml-intl.com/docs/specification/xml-tm.html).''']]'''
+ 
+ '''[[FS-''' Maybe I misunderstood. I had no problem with the construction of the ID value, e.g. as a combination of a string to identify the document plus a string to identify the element. I only worried about the validation mechanisms for cross-document IDs, which do not exist (see the statement below on xml:id). But if validation across documents is not necessary, but only retrieval, then we can state s.t. like "The IDs across documents are not used for schema based validation of uniqueness. Hence, cross-document validation of ID values is not an issue."''']]'''
+ 
  === Challenge/Issue ===
  
  In order to most effectively re-use translated text where content is re-used (either across update versions or across deliverables) it is necessary to have a unique and persistent id associated with the element.

Received on Wednesday, 15 June 2005 12:10:00 UTC