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, David RR Webber (XML) <david@drrw.info> wrote:
> Dave,
>
> Exactly!
>
> I'm stating the goals - to create an XML document format for technical
> document creation that combines DITA with ability to layout formatted text
> and graphic content with basic content handling motifs - example xhtml - but
> not to replace current page-orientated printed document storage formats.
> Instead page handling and rendering is specifically left to rendering tools.

I don't read that as a clear goal David.
It has too much creep into 'how'.

KISS principles.
"to create an XML document format for technical
 document creation "

I thought the goal was interchange, not creation?

No matter. What do you want from your XML format?
<guess>To get 'out' to another format</guess>
so that company B can comprehend my content.

Format A in,
Format B out.

Simple. Now what do you need to know about Format A semantics?




>
> Support for content authoring and adherence to a formal document structure
> model via XML is required.

I can't see why other than by remembering your prior emails.
I'd hope (perhaps even require) that Format A has a document structure?

Is content authoring in scope?
I'd vote against that for this TC.


> By providing XML structured content - scripted  process handling is enabled.

I don't understand that David.


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]