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 intended work?


On 10/04/07, Michael Priestley <mpriestl@ca.ibm.com> wrote:
>
> If we just used a presentation format for interchange, how would you preserve semantics, and how would you get a different look and feel?
>
> For example, if I pull a DocBook procedure into a DITA web, I'd like to be able to:
>  a) identify it as an equivalent to a DITA task, so I can do things like sort related links appropriately, and
> b) apply my own look-and-feel, including fonts, generated headings, headers/footers/standard navigation elements, etc.
>
> There are several degrees of interoperability:
> 1) sharing content: pull the content into my deliverable, applying my own look and feel, navigation etc. - this is relatively simple, but already requires more than PDF as source
> 2) sharing semantics: pull the content into my production system, including specialized semantic processing for specialized elements - like treating task steps in a different way from generic list items
> 3) sharing constraints: provide equivalent constraints on both sides of the interchange, so that you can get robust integration of processes, and not break down every time someone feeds you a supposed "DITA task" that breaks the processing expectations by e.g. allowing multiple lists of steps under a single title, or more than one level of step nesting.

I like this level of discussion more than microformats and pdf related TLA's.
I'd prefer to leave how until we share a terminology?

This is a user view which I find very helpful.






>
> One of the proposals currently in place, including an argument for using an XML hub format for interchange with preservation of semantics, is here:
> http://flatironssolutions.com/Downloads/DITA2007West.pdf - it provides a potential solution for 1) and 2); for 3), DITA has mechanisms for creating specialized content types that can match other existing standards while still processing as DITA content, which gives a potential solution for some cases at least.


Is there a page we could collect some of these terms and references
please Michael?

I don't want to be looking at solutions till I understand the problem
more clearly.

regards



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


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