Re: About UOML

[Michael Priestley <mpriestl@ca.ibm.com>]

Can you point us to some introductory
material? Even better, could you tell us how UOML would fit into the reuse
scenario we've been working to, which is:

- 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 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

"Wang Donglin" <dlwang@sursen.com>

03/30/2007 06:16 AM

Please respond to
dlwang@sursen.com

To	Michael Priestley/Toronto/IBM@IBMCA, "Scott Hudson" <scott.hudson@flatironssolutions.com>
cc	"mary.mcrae@oasis-open.org" <mary.mcrae@oasis-open.org>, "docstandards-interop-tech@lists." <docstandards-interop-tech@lists.oasis-open.org>, "Dee Schur" <dee.schur@oasis-open.org>
Subject	About UOML

Hi all,
UOML provide effective interoperability between different document format.
Before start a new TC, one need know more about UOML.

-Alex
Chair
OASIS UOML TC

>Thanks Michael! Here is another suggested wording:
>
>One of the benefits that XML touted from early in it's inception was
>that of platform independence. This independence greatly helped in
its 
>widespread adoption, yet brought with it the unintended consequence
of a 
>proliferation of standardized XML grammars. Document standards such
as 
>DITA (http://www.oasis-open.org/committees/dita), DocBook 
>http://www.oasis-open.org/committees/docbook), and ODF 
>(http://www.oasis-open.org/committees/office) all address a similar
need 
>to mark up documentation in a platform-independent format. Increasingly,
>organizations need to collaborate and share content with other 
>organizations. As a result, XML interoperability between these standards
>is critical. These standards, however, have not been designed with
>cross-standard interoperability in mind.The Doc Standards 
>Interoperability TC is intended to address the development and 
>documentation of scenarios for cross-standard content sharing; a 
>specification for an interoperability framework, including mappings
from 
>participating standard formats to the framework; and requirements on
>participating standards to improve interoperability.
>
>Best regards,
>
>--Scott
>
>Michael Priestley wrote:
>>
>> Last time we met we agreed that we would initiate the formation
of a 
>> technical committee, which starts with the formation of  a
formal 
>> public discussion list. I did submit the request, but Mary had
>> suggested an elaborated statement of scope which I haven't provided
yet.
>>
>> Here's an attempt at expanded information:
>>
>> Document standards such as DITA 
>> (http://www.oasis-open.org/committees/dita), DocBook 
>> http://www.oasis-open.org/committees/docbook), and ODF 
>> (http://www.oasis-open.org/committees/office) are designed to
enable 
>> standardized content that can be used across applications that
conform 
>> to the standard. However, this reuse does not typically cross
the 
>> boundaries of the standards, because the standards are not usually
>> designed with cross-standard interoperability in mind. Members
of the 
>> DITA, DocBook, and ODF TCs are forming a technical committee to
>> address this problem. The work of the technical committee is likely
to 
>> include the development and documentation of scenarios for 
>> cross-standard content sharing; a specification for an 
>> interoperability framework, including mappings from participating
>> standard formats to the framework; and requirements on participating
>> standards to improve interoperability.
>>
>> Is that ok with folks on the current list?
>>
>> Let's meet this Thursday to discuss taking the message back to
our 
>> respective TCs. My apologies for letting the proposal lag.
>>
>> Michael Priestley
>> IBM DITA Architect and Classification Schema PDT Lead
>> mpriestl@ca.ibm.com
>> http://dita.xml.org/blog/25
>>
>>
>> *"Scott Hudson" <scott.hudson@flatironssolutions.com>*
>>
>> 03/29/2007 12:46 PM
>>
>>                
 
>> To
>>                
 "Dee Schur" <dee.schur@oasis-open.org>
>> cc
>>                
 Michael Priestley/Toronto/IBM@IBMCA, 
>> <docstandards-interop-tech@lists.oasis-open.org>, 
>> <mary.mcrae@oasis-open.org>
>> Subject
>>                
 Re: [docstandards-interop-tech] Meeting next week?
>>
>>
>>
>>                
 
>>
>>
>>
>>
>>
>> I was going to ask the same question! Do we have everything we
need to 
>> initiate the formation of a TC? Are we going to set up regularly
>> scheduled meetings?
>>
>> --Scott
>>
>> Dee Schur wrote:
>> Just wondered what was going on with this group? What do we need
to do 
>> to create the discussion list?
>> Thanks,
>> Dee
>>  
>>
>> ------------------------------------------------------------------------
>>
>> *From:* Michael Priestley [_mailto:mpriestl@ca.ibm.com_] *
>> Sent:* Thursday, February 22, 2007 12:27 PM*
>> To:* _docstandards-interop-tech@lists.oasis-open.org_ 
>> <mailto:docstandards-interop-tech@lists.oasis-open.org>*
>> Subject:* [docstandards-interop-tech] Meeting next week?
>>  
>>
>> Please let me know what days/times would be available for a continuing
>> meeting - I'd like to set up a series of telecons to discuss plans
for 
>> this year and review some new work by Flatirons on an interoperability
>> framework.
>>
>> My default preference is for Thursday 2 PM ET
>>
>> Michael Priestley
>> IBM DITA Architect and Classification Schema PDT Lead_
>> __mpriestl@ca.ibm.com_ <mailto:mpriestl@ca.ibm.com>_
>> __http://dita.xml.org/blog/25_
>>
>> --
>> No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.5.441 / Virus Database: 268.18.3/697 - Release Date:
>> 2/22/2007 11:55 AM
>>
>> --
>> Internal Virus Database is out-of-date.
>> Checked by AVG Free Edition.
>> Version: 7.5.441 / Virus Database: 268.18.4/702 - Release Date:
>> 2/25/2007 3:16 PM
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: docstandards-interop-tech-unsubscribe@lists.oasis-open.org
>For additional commands, e-mail: docstandards-interop-tech-help@lists.oasis-open.org