RE: [docstandards-interop-tech] RE: [odf-adoption] Please review theDocstandards InterOp Scenerio and possible venues

I actually hadn't even thought of the
email software docs as being a book - I think I assumed it was a website,
or possibly singlesourced :-)

Part of my goal in having the policies
and procedures website was to underscore that DITA isn't specifically a
tech pubs standard, which I thought was a differentiator from DocBook.
Would it be enough to combat the book misperception if we explicitly said
"email software website"? 

Michael Priestley

IBM DITA Architect and Classification Schema PDT Lead



http://dita.xml.org/blog/25

"Dee Schur" <>

07/13/2006 03:25 PM

To

"'Dick Hamilton'" <>,
<>

cc

Subject

RE: [docstandards-interop-tech] RE:
[odf-adoption] Please review the Docstandards InterOp Scenerio and possible
venues

I agree, the misperceptions clearly persist. What
can we collectively do

about this?

Regards,

Dee Schur

Member Support

www.oasis-open.org

-----Original Message-----

From: Dick Hamilton [mailto:] 

Sent: Thursday, July 13, 2006 3:20 PM

To: 

Subject: RE: [docstandards-interop-tech] RE: [odf-adoption] Please review

the Docstandards InterOp Scenerio and possible venues

Here is an update to the scenario that simplifies it based on my

comments in the meeting today.  All I did was to remove the second

import of a DITA fragment and the reference to it in the last item.

The only other comment I have, which I'll toss out for discussion,

is that this tends to reinforce common (mis)perceptions about DITA

and DocBook (e.g., modules vs. books).  We might want to consider

working against those perceptions to show the flexibility of each

of the standards.  For example, we might generate the email software

docs from DITA and the website from DocBook.  Just a thought for your

consideration.

Regards,

Dick Hamilton



========================================================================

======

- govt worker begins drafting a policy note in ODF about the use of

personal data received via email 

- govt worker pulls in the text of the relevant statute, which is in a

DITA specialization 

- govt worker pulls in the instructions on how to include the text of

the disclaimer in emails, from documentation of the email software

written in DocBook 

- technical author 1, using DITA, creates an internal policy and

procedures website 

- and pulls in text from the DocBook email software documentation 

- and pulls in the legal text from a DITA specialization 

- and pulls in the relevant section of the policy note, written in ODF

- technical author 2, using DocBook, creates a customized version of the

email software documentation 

- and pulls in portions of the procedures web site, in the form of DITA

topics and ODF policy notes 

- as the policy changes, or the email software changes, or the statute

itself changes, all the references can be updated simply by

rebuilding/republishing the content, since all reuse is by reference not

by copy-and-paste 

---------------------------------------------------------------------

To unsubscribe, e-mail:



For additional commands, e-mail:



-- 

No virus found in this incoming message.

Checked by AVG Free Edition.

Version: 7.1.394 / Virus Database: 268.9.10/387 - Release Date: 7/12/2006

 

-- 

No virus found in this outgoing message.

Checked by AVG Free Edition.

Version: 7.1.394 / Virus Database: 268.9.10/387 - Release Date: 7/12/2006

 

---------------------------------------------------------------------

To unsubscribe, e-mail: 

For additional commands, e-mail: