W3C home > Mailing lists > Public > public-i18n-its@w3.org > April to June 2006

[Bug 3058] ITS inheritance mechanism versus other inheritance mechanisms (e.g. DITA): Need for clear distinction

From: <bugzilla@wiggum.w3.org>
Date: Wed, 12 Apr 2006 07:32:16 +0000
To: public-i18n-its@w3.org
Message-Id: <E1FTZpo-0008Cg-NP@wiggum.w3.org>


------- Comment #4 from fsasaki@w3.org  2006-04-12 07:32 -------
(In reply to comment #3)
> 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.
However, what we could do is show workarounds for these cases, like saying "put
all DITA files in one directory and apply the rules to them." That would in
practice be leveling of the difference between the compound and non-compound
version of <note>.
Having such an example would make it easier to sell ITS to DITA.
Received on Wednesday, 12 April 2006 07:32:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:04:09 UTC