Am Freitag, den 01.09.2006, 11:14 -0400 schrieb Bruce D'Arcus: > [...] > > As I at least am envisioning enhanced metadata, the location of the > representation is largely irrelevant, and mostly just a question of > convenience. So think about the ctiation case: in text, you have a URI > ID. That URI could be some resolvable URL, it could be a more abstract > URI (like a URN) that a tool can resolve somewhere else, or it could > also be used to identify the embedded metadata description as a way to > link the two.
As far as I understand you, what you want is to embed metadata in one specific document. This is not the case with smarttags. A keyword X in any document will be handled in the same way. > E.g. if I am understanding you right, maybe there is room to consider > both the same kind of use case? You use the smart tags here to enable > a piece of document content to be in some way associated with some > data-related application-dependent (NOT document data related) > action or > representation. The word itself looks like any other word. It does and can not change representation (if it were to, 1) the recognizer wouldn't recognize it any more and 2) you couldn't see/edit it anymore ), so in the end it wouldn't be a normal word. > > In the inventory case, you're somehow connecting to a record somewhere > (an online database? maybe tying into XForms? I dunno) to accomplish > some task (user wants to see or edit the record maybe). Yes, kind of, in the case of Smart Tags loadable libraries can do whatever action is desired. > In the > citation case, we need to allow tools to grab a data representation in > order to process the output for display. I don't quite follow you. Who creates data representations and where will it be displayed? -- Jakob Lechner Research & Development Fabalabs Software GmbH Honauerstraße 4 A-4020 Linz Tel.: [+43] (70) 60 61 62 Fax: [+43] (70) 60 61 62-609 E-Mail: [EMAIL PROTECTED] Web: http://www.fabalabs.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
