OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita-translation message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Fw: Updated Acronym Proposal posted

Forwarding Erik's response to Felix so it gets into the archives.

Robert D Anderson
IBM Authoring Tools Development
Chief Architect, DITA Open Toolkit
(507) 253-8787, T/L 553-8787 (Good Monday & Thursday)
----- Forwarded by Robert D Anderson/Rochester/IBM on 02/01/2008 01:09 PM
             M                                                          To 
                                       Felix Sasaki <fsasaki@w3.org>       
             02/01/2008 12:42                                           cc 
             PM                        bhertz@sdl.com, Bryan Schnabel      
                                       om, KARA@CA.IBM.COM,                
                                       jogden@ptc.com, Robert D            
                                       Re: Updated Acronym Proposal posted 
                                       (Document link: Robert D Anderson)  

Hi, Felix:

Here's the approved controlled values proposal, which can define simple
enumerations but can also scale up to define hierarchical (taxonomic)
relationships between concepts:


Yes, <glossAlt> captures an alternate term for the same meaning.

The association of a glossentry topic defining a term sense with a Wordnet
sysnset would just be a special case of linking (where the link indicates a
processable relation rather than just traversal to a new document).  So,
one way to do that would be to use a related link within the glossentry
topic, as in the following example:

... <glossentry id="usbfd">
....... <glossterm>USB flash drive</glossterm>
....... <glossdef>A small portable drive.</glossdef>
....... <glossBody> ... </glossBody>
....... <related-links>
........... <link format="html" role="other" otherrole="equivalent" href="
............... <linktext>Nonvolatile storage</linktext>
........... </link>
....... <related-links>
... </glossentry>

Probably there is a better URL for the synset rather than the lexical
label, but you get the idea.

Anyway, many times, the relationship won't be exact equivalence but instead
a kind-of or part-of relationship.  For that reason, I'd suggest instead
using the specialized map provided by the controlled values proposal to
specify the link:

... <subjectScheme>
....... <subjectdef format="html" navtitle="Nonvolatile storage" href="
........... <hasKind>
............... <subjectdef navtitle="USB flash drive" href="usbfd.dita"/>
............... references to other hyponyms of "Nonvolatile storage"
defined locally or elsewhere
........... </hasKind>
....... </subjectdef>
....... references to other hypernyms defined by WordNet, by local
glossentry topics, or elsewhere
... </subjectScheme>

In fact, it should be possible to convert the core of WordNet into a set of
DITA glossentry topics related by a DITA subjectScheme map, thus making the
WordNet sense definitions available for local processing in a DITA XML

Hoping that's interesting,

Erik Hennum

> Felix Sasaki <fsasaki@w3.org>
> 01/29/2008 05:30 PM
> Subject
> Re: Updated Acronym Proposal posted
> Hello Robert or others,
> I have a question about
> "The enumeration is validated by means of the proposed controlled values
> mechanism"
> and "(Please see the Proposal 12031 for Controlled Values.)"
> is the formulation of this proposal available?
> Also I saw the requirement "List synonyms, abbreviations, acronyms, and
> other alternative terms with the same meaning. (Called a synomym set by
> WordNet; please see http://en.wikipedia.org/wiki/Synsets.)"
> If I understand correctly, the <glossAlt> element is used for this
> purpose. My question here is: is it possible to have here reference to
> an external source, e.g. an WordNet entry, and if yes, is it possible to
> specify what kind of processing is needed for such a reference? In the
> case of WordNet you might not point to a lexical item directly but to an
> identifier of a sysnset The necessary processing would be the resolution
> of an appropriate lexical item from that identifier.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]