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

[ESW Wiki] Update of "its0504ReqLinkedText" by ChristianLieske

From: <w3t-archive+esw-wiki@w3.org>
Date: Thu, 19 May 2005 14:12:55 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050519141255.24407.79405@localhost.localdomain>
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 ChristianLieske:
http://esw.w3.org/topic/its0504ReqLinkedText


------------------------------------------------------------------------------
  
  '''[[MI-''' However, how to retrieve the linked data should be an seperate issue. It's not just an authentication issue. Accessing to external data may require a specific access parameters, URL, ane even a specific application. How to access to external data should be left to a rendering application or process. When the Linked Tag has something like ''src=/database/formItems/description@pk=123'', how to access to the data in the description field of the formItems table should be taken care of by a rendering tool or a localization tool. ''']]'''
  
+ '''[CL] As mentioned during the 19 May 05 conf call: From my understanding, we are looking at two requirements
+ 
+ a. markup which allows us to say 'the content here originates somewhere else'
+ b. identification/access information related to the markup (this might be something simple like a GUID, or something more complex like all information necessary to actually log on to a terminology management system and navigate to a term stored in the system)
+ 
+ Example:
+ 
+ See also <originatesElsewhere infoId="42">Work with Voucher</originatesElsewhere>
+ 
+ <info>
+  <general system="MYSystem" database="DB4" user="xxx" password=""/>
+  <entry id=42" termInDB="4444"/>
+ </info>'''
  
  == Challenge/Issue ==
  
Received on Thursday, 19 May 2005 14:36:01 GMT

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