RE: DITA acronym proposal: unification with related proposals

["JoAnn Hackos" <joann.hackos@comtech-serv.com>]

Hi Deborah,

Can you temporarily join the Translation SC? That will give you access to our mailing list as a whole.

 

'dita-translation@lists.oasis-open.org'

 

We also have a supplementary list of W3C members such as Felix and Richard. I'm happy to forward to them.

 

I don't know if we're ready yet for the TC discussion. Andrzej, what do you think?

JoAnn

 

PS We meet on Monday morning at 8 Pacific time. Can you join?

 

JoAnn

 

JoAnn T. Hackos, PhD
President
Comtech Services, Inc.
710 Kipling Street, Suite 400
Denver CO 80215
303-232-7586
joann.hackos@comtech-serv.com

 

 

---

From: Deborah_Pickett@moldflow.com [mailto:Deborah_Pickett@moldflow.com]
Sent: Tuesday, July 24, 2007 6:47 PM
To: Andrzej Zydron - XML-INTL
Cc: JoAnn Hackos; Kara Warburton; Rodolfo M. Raya
Subject: Re: DITA acronym proposal: unification with related proposals

Hi Andrzej, 

Thanks for writing back.  I took a look at the 
proposal.  The only stumbling block that I can perceive is the choice of 
which elements to specialize from.  Ruby will want to specialize from 
something other thank <keyword>, for instance.  Collation overrides 
will want to specialize from <ph>, probably.  Both ruby and collation 
overrides will want a generic inline content model to allow nested <b> and 
<tm> and <keyword> and so on.  My example markup assumed a new 
base element <annotation>, but that need not be the best way. 

I agree with Robert's comments in the 
proposal about <data> not being a good choice because it's more 
metadata-esque than what any of us want, but I'd even go so far to say that 
<data> isn't a good base for <short> either, particularly since the 
examples in the acronym proposal sometimes print that text. 

Maybe JoAnn knows best: who should be involved in the 
overall ruby/abbreviation discussion?  Is there I list I can join? 
 Presently I am targeting individuals but that's not really scalable. 
 Or should this be promoted to the dita TC list? 

(Unrelated: I have some ideas on how to resolve the 
capitalization-during-translation issue.  Where should I send such 
comments?) 

-- 
Deborah 
Pickett
Information Architect, Moldflow Corporation, 
Melbourne
Deborah_Pickett@moldflow.com 

Andrzej Zydron - XML-INTL <azydron@xml-intl.com> wrote on 
07/24/2007 06:45:57 PM:

> Hi Deborah,
> 
> Thank you for 
your email. It looks as if we have a couple of threads
> coming together 
here. The latest version of the current proposal can
> be found 
here:
> 
> 
http://wiki.oasis-open.org/dita/TranslationSubcommittee/Acronyms
> 
> Although this is still currently under review.
> 
> Best 
Regards,
> 
> AZ
> 
> Deborah_Pickett@moldflow.com 
wrote: 
> 
> Hi Andrzej, 
> 
> You submitted a proposal for dealing with acronyms in DITA 
(http:
> 
//lists.oasis-open.org/archives/dita-translation/200703/msg00017.html
> ) 
a little while ago. 
> 
> I don't know what stage it's at, but 
recent discussions that I have 
> been having with some of the W3C 
translation sub-committee about 
> ruby led me to realize that there is a 
common thread that connects 
> the two ideas.  Additionally, markup 
for glosses and for overriding 
> collation values for text could also 
come from this. 
> 
> The common idea is that all of these concepts 
express a "basic" text
> as well as one (or more) "annotations", which in 
some cases is 
> visible in the output and in some cases is not.  For 
abbreviations, 
> the short text is the base, and the spelled-out version 
the 
> annotation (or vice versa?).  For ruby, the Kanji characters 
are the
> base, and the pronunciation key the annotation.  For 
collation 
> overrides, the text to display is the base, and the collation 
value 
> (never printed) is the annotation. 
> 
> I propose 
that acronyms/abbreviations, ruby, and collation overrides
> all be 
specified as domain specializations of this "annotation" 
> base. 
 Some sample code might give you an idea (with class 
> attributes 
shown to demonstrate the inheritance).  The element names
> and 
content models are, of course, negotiable. 
> 
> <abbreviation 
class="+ topic/annotation abbrev-d/abbreviation "> 
>   <abbrev 
class="+ topic/annotation-base abbrev-d/abbrev ">W3C</abbrev> 
> 
  <abbreviation-expansion class="+ topic/annotation-text abbrev-
> 
d/abbreviation-expansion ">World Wide Web 
Consortium</abbreviation-expansion>
> </abbreviation> 
> 
> <abbreviation class="+ topic/annotation abbrev-d/abbreviation "> 
>   <abbrev-container class="+ topic/annotation-base-container 
abbrev-
> d/abbrev-container "> 
>     <abbrev 
class="+ topic/annotation-base abbrev-d/abbrev ">W</abbrev> 
> 
    <abbrev class="+ topic/annotation-base abbrev-d/abbrev 
">W</abbrev> 
>     <abbrev class="+ 
topic/annotation-base abbrev-d/abbrev ">W</abbrev> 
>   
</abbrev-container> 
>   </abbreviation-expansion-container 
class="+ topic/annotation-text-
> container 
abbrev-d/abbreviation-expansion-container "> 
>     
<abbreviation-expansion class="+ topic/annotation-text abbrev-
> 
d/abbreviation-expansion ">World</abbreviation-expansion> 
> 
    <abbreviation-expansion class="+ topic/annotation-text 
abbrev-
> d/abbreviation-expansion 
">Wide</abbreviation-expansion> 
>     
<abbreviation-expansion class="+ topic/annotation-text abbrev-
> 
d/abbreviation-expansion ">Web</abbreviation-expansion> 
>   
</abbreviation-expansion-container> 
> </abbreviation> 
> 
> <ruby class="+ topic/annotation ruby-d/ruby "> 
> 
  <rb class="+ topic/annotation-base ruby-d/rb ">東京</rb> 
>   <rt class="+ topic/annotation-text ruby-d/rt 
">とうきょう</rb> 
> </ruby> 
> 
> <ruby class="+ 
topic/annotation ruby-d/ruby "> 
>   <rbc class="+ 
topic/annotation-base-container ruby-d/rbc "> 
>     <rb 
class="+ topic/annotation-base ruby-d/rb ">東</rb> 
>   
  <rb class="+ topic/annotation-base ruby-d/rb ">京</rb> 
>   </rbc> 
>   <rtc class="+ 
topic/annotation-text-container ruby-d/rtc "> 
>     <rt 
class="+ topic/annotation-text ruby-d/rt ">とう</rb> 
>   
  <rt class="+ topic/annotation-text ruby-d/rt ">きょう</rb> 
>   </rtc> 
> </ruby> 
> 
> 
<collate class="+ topic/annotation collate-d/collate "> 
>   
<collate-base class="+ topic/annotation-base collate-d/collate-
> base 
">The Alan Parsons Project</collate-base> 
>   
<collate-as class="+ topic/annotation-text collate-d/collate-
> 
as">Parsons, Alan</collate-as> 
> </collate> 
> 
> What do you think? 
> 
> -- 
> Deborah 
Pickett
> Information Architect, Moldflow Corporation, Melbourne
> 
Deborah_Pickett@moldflow.com 
> 

> -- 
> 
> 
> email - 
azydron@xml-intl.com
> smail - c/o Mr. A.Zydron
>    PO 
Box 2167
>         Gerrards Cross
>   
      Bucks SL9 8XF
>    United Kingdom
> 
Mobile +(44) 7966 477 181
> FAX    +(44) 1753 480 465
> 
www - http://www.xml-intl.com
> 
> This message contains 
confidential information and is intended only
> for the individual named. 
 If you are not the named addressee you
> may not disseminate, 
distribute or copy this e-mail.  Please
> notify the sender 
immediately by e-mail if you have received this
> e-mail by mistake and 
delete this e-mail from your system.
> E-mail transmission cannot be 
guaranteed to be secure or error-free
> as information could be 
intercepted, corrupted, lost, destroyed,
> arrive late or incomplete, or 
contain viruses.  The sender therefore
> does not accept liability 
for any errors or omissions in the contents
> of this message which arise 
as a result of e-mail transmission.  If
> verification is required 
please request a hard-copy version. Unless
> explicitly stated otherwise 
this message is provided for informational
> purposes only and should not 
be construed as a solicitation or offer.
> 
> 
> 
> 
[attachment "azydron.vcf" deleted by Deborah A Pickett/MOLDFLOW]