Hi Deborah,
Thank you for your reply and explanation. You are correct - xml:tm
looks as if it is orthogonal to the proposal, although it well worth
mentioning in terms of the overall point of text reuse. Regarding DITA
namespace there is a very simple technique to make xml:tm namespace
transparent, although in the long run having DITA namespace aware will
allow for the use of other useful vocabularies such as Ruby etc.
Best Regards,
AZ
Deborah_Pickett@moldflow.com wrote:
OFA67B3976.E034E0D4-ONCA257352.002C2581-CA257352.002EDBD8@moldflow.com"
type="cite">
Hi Andrzej,
(Leaving aside technical issues such
as the fact that DITA isn't namespace-aware yet...)
I've reviewed the xml:tm standard
specification
to which you link, but I fail to see the connection. The introduction
states that xml:tm handles text units, which are at no finer than the
sentence
level of granularity (which I assume means that a text unit equates to
a translation unit when translation is involved). Some use scenarios
for DITA proposal #12020 are for pieces much smaller than sentences:
individual
words, perhaps phrases. It doesn't look like xml:tm has containers
for such small things (which makes sense given its focus on
segmentation
and translation units).
But IMO the main point of #12020 is
not re-using text, but about expanding the content model of
text-containing
elements to allow (specializations to achieve) more useful nesting (for
instance, by restricting away mixed content). To me, xml:tm seems
to be orthogonal to #12020.
If I've completely missed the point
of xml:tm then please let me and the TC list know.
--
Deborah Pickett
Information Architect, Moldflow Corporation, Melbourne
Deborah_Pickett@moldflow.com
Hi,
This whole issue is addressed by the LISA OSCAR xml:tm standard, by use
of the xml:tm namespace. This is a completely comprehensive solution to
this issue (covering all text issues such as translatable attributes,
within text and subflow issues), as opposed to the incomplete
suggestions to date. The xml:tm standard mandates the use of X3C ITS
document rules for establishing the identification and treatment of
text
for a given XML vocabulary. We should not be reinventing existing
standards:
http://www.lisa.org/standards/xmltm/
Best Regards,
AZ
Stan Doherty wrote:
> Hi --
>
> At the last TC meeting, attending members converged on a new
strategy
> for addressing this issue. I took the action item to summarize the
new
> strategy and to send that summary out to the list for further
review
> and discussion.
>
> 1. The original scope for 12020 needs to be expanded beyond the
> nesting of keyword. Although nested keywords would provide one
> solution, it does not address many of use cases for reusing bits
of
> text outside teh context of keywords, e.g. reusing a text bit in
> <uicontrol>.
>
> 2. Micheal Priestley proposed that DITA 1.2 add the <text>
element
to
> both <keyword> and <ph>. This fairly restricted
implementation
would
> allow for reuse of <text> without creating more general
confusion
> about exporting semantic or non-semantic applications of
<keyword>
and
> <ph> inappropriately. Specializations of <keyword> and
<ph> would
> inherit <text>.
>
> 3. Eliot suggested that we audit DITA 1.2 for situations where
> (#PCDATA) is not allowed. In those situations we need to verify
that
> <keyword> or <ph> are allowed.
>
> If you have comments, use cases, or alternate approaches, please
send
> them out to the list.
>
> Pax,
> Stan Doherty
--
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.
--
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.
|