W3C home > Mailing lists > Public > public-i18n-its@w3.org > July to September 2005

[ESW Wiki] Update of "its0505ReqUniqueID" by YvesSavourel

From: Richard Ishida <ishida@w3.org>
Date: Mon, 22 Aug 2005 09:36:13 +0100
To: <public-i18n-its@w3.org>
Message-Id: <20050822083614.BE7BD4EF34@homer.w3.org>


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 YvesSavourel:
http://esw.w3.org/topic/its0505ReqUniqueID

------------------------------------------------------------------------------
  
  === Summary ===
  
- It should be possible to attach a unique identifier to any localizable item. This identifier should be unique within a document set, but should be identical across all translations of the same item.
+ [R004] It should be possible to attach a unique identifier to any localizable item. This identifier should be unique within a document set, but should be identical across all translations of the same item. 
  
  
- === Challenge/Issue ===
+ === Challenges/Issues ===
  
  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 identifier associated with the element.
  
  This identifier allows the translation tools to correctly track an item from one version or location to the next. After one is sure that this is the same item, the content can be examined for changes, and if no change has taken place the potential for re-use of the previous translation is very high.
  
- Change analysis constitutes an extremely powerful productivity tool for translation when compared to the typical source matching (a.k.a. translation memory) techniques, which simply look for similar source text in the database without, most of the time, being able to tell whether the context of its use is the same. 
+ Change analysis constitutes an extremely powerful productivity tool for translation when compared to the typical source matching (a.k.a. translation memory) techniques, which simply look for similar source text in the database without, most of the time, being able to tell whether the context of its use is the same.
  
- This change analysis technique has been possible with user-interface messages in the past, but the introduction of structured XML (and SGML) documents will allow for its use in documents also. 
+ This change analysis technique has been possible with user-interface messages in the past, but the introduction of structured XML (and SGML) documents will allow for its use in documents also.
- 
  
  === Notes ===
  
- The xml:id attribute defined here [http://www.w3.org/TR/xml-id/] (Currently a Proposed Recommendation) may be a mean to carry the unique identifier. Note however, that xml:id is unique within a document, not necessarily within a set of documents.
+ The xml:id attribute [XML ID][http://www.w3.org/TR/xml-id/] may be a means to carry the unique identifier.
  
- [[RI but with a URI+id you usually would get a unique identifier.]]
+ Note that, while an xml:id value is unique within a document and not necessarily within a set of documents, combining the xml:id value with the URI of the document would ensure a globally unique identifier.
  
  
  === Quick Guidelines ===
@@ -46, +45 @@

  
   * Using URIs, where the in-document ID is a fragment identifier.
  
- The requirement can be fulfiled by the following XQuery user defined function:
+ There are various ways to check for unique IDs in a document. For example, the following XQuery user defined function:
  
  {{{
  query version "1.0";
Received on Monday, 22 August 2005 08:36:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:12:45 GMT