<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>3058</bug_id>
          
          <creation_ts>2006-03-29 14:32:10 +0000</creation_ts>
          <short_desc>ITS inheritance mechanism versus other inheritance mechanisms (e.g. DITA): Need for clear distinction</short_desc>
          <delta_ts>2006-07-24 10:35:41 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>ITS</product>
          <component>ITS tagset</component>
          <version>WorkingDraft</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Windows XP</op_sys>
          <bug_status>CLOSED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Felix Sasaki">fsasaki</reporter>
          <assigned_to name="Felix Sasaki">fsasaki</assigned_to>
          
          
          <qa_contact name="Felix Sasaki">fsasaki</qa_contact>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>8942</commentid>
    <comment_count>0</comment_count>
    <who name="Felix Sasaki">fsasaki</who>
    <bug_when>2006-03-29 14:32:10 +0000</bug_when>
    <thetext>Part of DITA sub TC, discussion of proposal for the xml:lang attribute:
[[
       -- We&apos;re talking about the root topic element.
        -- If xml:lang is on document element, then the highest level topic 
            element inherits xml:lang. Likewise, &lt;topicref&gt; should inherit 
            from &lt;map&gt; (if no parent overrides xml:lang) or from nearest 
            parent that overrides the xml:lang setting of the root element.
        -- In case of contradiction between xml:lang setting on &lt;topicref&gt; and 
            xml:lang on &lt;topic&gt;, the &lt;topicref&gt; setting does not apply to the 
            &lt;topic&gt;. In other words, the map does not override any xml:lang 
            on the &lt;topic&gt;.
        -- Discussion whether xml:lang on map should apply to the topics...
        -- Discussion of translation workflow...
        -- Need map file for each target language.
        -- Proposal must clarify the following:
            - xml:lang on &lt;map&gt; is applied to the map.
            - xml:lang on &lt;map&gt; does not affect topics.
            - if different xml:lang values exist on map and topic, topic setting
                overrides.
            - add use cases]]

The usefulness of our global rules might be quite limited for DITA, due to DITA&apos;s specific inheritance mechanism (see discussion above). We need to make clear for DITA and other markup vocabularies with specific inheritance mechanisms, how ITS fits into the picture. IMO we don&apos;t need to adapt to them. However, a detailed example of the relation between inheritance in DITA versus inheritance in ITS would be good. I&apos;d propose Christian to deliver one :)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9082</commentid>
    <comment_count>1</comment_count>
    <who name="Yves Savourel">ysavourel</who>
    <bug_when>2006-04-07 20:16:43 +0000</bug_when>
    <thetext>
As far as I understand there is no issue here.
Shall we close this bug?
-ys
</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9109</commentid>
    <comment_count>2</comment_count>
    <who name="Felix Sasaki">fsasaki</who>
    <bug_when>2006-04-10 15:50:29 +0000</bug_when>
    <thetext>(In reply to comment #1)
&gt; As far as I understand there is no issue here.
&gt; Shall we close this bug?
&gt; -ys
&gt; 

I had a look at 
http://norman.walsh.name/2005/10/21/dita#conref
and I am still wondering: what happens with translatability information if I apply the conref mechanism of DITA?

Examples from DITA: compare
1) &lt;note conref=&quot;#topic1/usefulnote&quot;/&gt;
versus
2) &lt;note&gt;&lt;p&gt;...&lt;/p&gt;&lt;/note&gt;
if I write a rule like
&lt;its:translateRule its:select=&quot;//note&quot; its:translate=&quot;no&quot;/&gt;
in ITS, the translatability information would inherit to the &lt;p&gt; element in the case of 2), but not in the case of 1).
However, if I understand DITA correct, 1) and 2) should behave the same in terms of translatability.
Am I missing something, or do we have to tell the DITA folks that they can&apos;t apply ITS in a useful way if they use @conref? </thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9110</commentid>
    <comment_count>3</comment_count>
    <who name="Yves Savourel">ysavourel</who>
    <bug_when>2006-04-10 16:23:47 +0000</bug_when>
    <thetext>
ITS is applied to the *source* document, without pertending knowing anything about how the documents are merged/split/reorganized to form a final document.

This is a limitation that comes with any type of compound-document system, not just DITA. But there is not much we can do about it. Anyone can create document from bit and pieces of other documents using various methods: there are no way we could forsee all cases.

Re-usability has many advantages, but it has also drawbacks.
</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9180</commentid>
    <comment_count>4</comment_count>
    <who name="Felix Sasaki">fsasaki</who>
    <bug_when>2006-04-12 07:32:16 +0000</bug_when>
    <thetext>(In reply to comment #3)
&gt; ITS is applied to the *source* document, without pertending knowing anything
&gt; about how the documents are merged/split/reorganized to form a final document.
&gt; 
&gt; This is a limitation that comes with any type of compound-document system, not
&gt; just DITA. But there is not much we can do about it. Anyone can create document
&gt; from bit and pieces of other documents using various methods: there are no way
&gt; we could forsee all cases.
&gt; 
&gt; Re-usability has many advantages, but it has also drawbacks.
&gt; 
However, what we could do is show workarounds for these cases, like saying &quot;put all DITA files in one directory and apply the rules to them.&quot; That would in practice be leveling of the difference between the compound and non-compound version of &lt;note&gt;.
Having such an example would make it easier to sell ITS to DITA.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9533</commentid>
    <comment_count>5</comment_count>
    <who name="Felix Sasaki">fsasaki</who>
    <bug_when>2006-05-01 07:00:40 +0000</bug_when>
    <thetext>Resolved by paragraph about inclusion mechanisms in the terminology / definition section, see http://www.w3.org/International/its/itstagset/itstagset.html#notation-terminology .
- Felix</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10682</commentid>
    <comment_count>6</comment_count>
    <who name="Felix Sasaki">fsasaki</who>
    <bug_when>2006-07-24 10:35:41 +0000</bug_when>
    <thetext>Closed, no further action necessary.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>