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

 


Help: OASIS Mailing Lists Help | MarkMail Help

docstandards-interop-discuss message

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


Subject: Re: [docstandards-interop-discuss] Clarifications / Scope of the intendedwork?



Hi Dave,

The focus is on XML documents. Here's an example business scenario:

- govt worker begins drafting a policy note in ODF with the subject "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 legal disclaimer which must now be included in every government email reply, from a different 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

Michael Priestley
IBM DITA Architect and Classification Schema PDT Lead
mpriestl@ca.ibm.com
http://dita.xml.org/blog/25



"Dave Pawson" <dave.pawson@gmail.com>

04/10/2007 08:57 AM

To
docstandards-interop-discuss@lists.oasis-open.org
cc
Subject
Re: [docstandards-interop-discuss] Clarifications / Scope of the intended work?





Hi Michael.

On 10/04/07, Michael Priestley <mpriestl@ca.ibm.com> wrote:

> The intent is to share document-oriented content between organizations. For example, DocBook, ODF, or DITA content - human-readable documents.

Or others commonly used for 'shared' documents?




> The purpose of the proposed TC is to identify the common denomenator, and to create mechanisms for identifying differences and commonalities within customized versions of the standards.

Are you (initially at least) constraining the TC work to XML based standards?


>So: we want to define ways to interoperate at the level of standards
definition, so that when people at the level of content creation hit
an interoperability problem, there's a clearly defined path for
solving it. IE, we want a standardized solution to cross-standards
problems - specifically those to do with sharing of content in
document-oriented standards such as DocBook, ODF, and DITA.

I'm still a little unclear Michael. Could you perhaps provide your
rationale for this?
I.e. define ways to interoperate  so that ......
Is the end goal a way for company A and B to access common data, or to get
from format A to B for human consumption, or so that documents laid down on
disk are accessible in n years time?
I.e. there could still be lots of 'why' answers even behind your clear terms?






> >So - I believe you are discussing formalizing mechanisms for the latter - PDF, xdoc, odp and other rich document formats using XML?
>
> Specifically we want to formalize mechanisms for exchanging content between organizations or applications that are using different XML document standards - so not PDF per se, but ODF, DITA, and DocBook, for a start, and hopefully others as we progress.


So the constraint is on XML sourced documents? That would / could include ODF
and MS OOXML etc?

regards


--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

---------------------------------------------------------------------
To unsubscribe, e-mail: docstandards-interop-discuss-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docstandards-interop-discuss-help@lists.oasis-open.org




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