Seth, I do believe that the motivation for
peeling away the base package has substantial value, namely, providing the
simplest possible setup for implementers to get their feet wet and figure out
how it all works before delving into the daunting
complexities.
Presenting the training stuff separately
also has value, since many existing and new users will not want to have to wade
past a raft of new elements and attributes that they never
use.
The problem you identify, Kristen, could
best be solved using simplified topic types in 1.3, intermediate between
<topic> and the current C/T/R types. For now, we may have to tell
them that if they want to use the sources of the base docs as examples of how
it's done, they'll have to do so in context of the more extensive package that
is equivalent to 1.1.
/Bruce
From: Kristen James Eberlein
[mailto:]
Sent: Wednesday, August 26, 2009 11:08
AM
To: DITA TC
Subject: [dita] Some practical problems
related to packaging
I've assumed that all packages will include the DITA
source files for the documentation, in addition to the DTDs and
documentation.
This presents a problem for the base package, since many
(if not all) of the source files for the base documentation are of type
concept and
reference.
Thoughts?
Kris
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates
this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
From: Park Seth-R01164
[mailto:]
Sent: Wednesday, August 26, 2009
11:33 AM
To: DITA TC
Subject: RE: [dita] Some practical
problems related to packaging
I've stayed out of the packaging discussion because I
couldnt care less about how many ways we try to arbitrarily package the
resources we create.
We've spent a huge amount of time on an issue with
little (if any) return value.
Let's deliver one DITA 1.2 package with everything that
the TC is willing to put our name on.
-seth
