OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-adoption message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [dita-adoption] DITA 1.2 compliant CMS


In all of my recent discussions with CMS vendors, I've asked about support
for DITA 1.2. The answer I've most frequently received is "We're studying
the spec and deciding what we can and will implement." We have been told
that a particular CMS, for example, will not have support for keyref in the
immediate future. Or, that there will not be support for all or several of
the 1.2 features. Quite clearly, there is work that CMS vendors must do to
conform to the new 1.2 features that is not simple or obvious.

We continue to find CMS vendors who claim to be DITA compliant but who do
not support even the most basic functionality. All they do, apparently, is
import and export DITA files. Nothing happens between the ears. Yet, they
are selling their products as DITA ready.

So what does DITA compliant then mean? We are, of course, working on this
issue in the TC. Companies ask us how they can write their RFPs so ensure
that they're not being fooled about DITA support in the CMS.

Is that what we intend by compliance? I think compliance is a much more
legalistic term but we do mean that something must be in place to support
DITA satisfactorily.

JoAnn


On 9/9/10 9:33 AM, "Paul Grosso" <pgrosso@ptc.com> wrote:

> Reading our DITA 1.2 Status article at
> http://www.oasis-open.org/committees/download.php/38956/DITA12SpecStatus
> Update.pdf
> someone has seen the comment in the second para of the
> "DITA 1.2 Readiness for Use" section that says that
> certain CMS vendors have announced upcoming DITA 1.2
> support and the comment near the bottom of the article
> urging CMS vendors to move quickly to support DITA 1.2
> and raised the question of what it means for a CMS to be
> DITA compliant (much less support DITA 1.2 in particular).
> 
> I have to admit I didn't think much about these statements
> when I reviewed this article.  I don't think about CMS's
> much at all.  They are just data bases to me, and the
> ability to work with DITA in particular or XML in general
> rarely has anything to do with the data base, it has to
> do with the application that knows how to put things into
> the data base and take it out of the data base.  In our
> case, that's the Arbortext Editor and CMS adapter front end.
> 
> In fact, on our "Fact Sheet" wiki page at
> http://wiki.oasis-open.org/dita-adoption/factSheet
> in the "Support for management of topics within a repository"
> section I long ago questioned the CMS section there, but we
> have never discussed my issues with that page.
> 
> So I'm back to asking what it might mean for a CMS
> to be DITA 1.2 compliant.
> 
> paul
> 
> 
> ---------------------------------------------------------------------
> 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
> 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]