Clarifications / Scope of the intended work?

["David RR Webber \(XML\)" <david@drrw.info>]

Folks,

 

I'm just reviewing this - please see my comments and notes below,

 

Thanks, DW

 

"Increasingly, organizations need to collaborate and share content with
other organizations. As a result, XML interoperability between these standards is critical."

 

>>> Increasingly? I think the collaborative world has been upon us for the past several years here already!

>>> "between these standards" does not make sense - I think you mean "between these organizations own standards.."

 

These standards, however, have not been designed with cross-standard interoperability in mind.

 

>>> Again this is not clear - I presume you mean the organizations own practice and use of XML - not XML persay?

 

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.

 

>>> This mostly works - the last part of the sentence after "framework;" - on participating standards"

>>> should this be participating in/with standards? Or the participating should "developing" instead?

 

Then the last but MOST crucial question - what kind of content sharing are we talking about here?

 

If it is business transactional XML - then obviously OASIS has ongoing relevant work such as CAM and BCM, where frameworks clearly can be carved out for use cases - and templates and patterns provided there in tandem with that work.

 

However - I suspect you are referring to document exchanges of free formatted informational content such as legal documents, bid letters, technical manuals, informational documents, technical procedures, catalogues, brochures, literature and other non-transactional content exchanges?

 

Obviously there you can provide templates also and content headers, classifications and structure and content hinting - but it is of necessity a model where the content is much more relaxed and freeform.

 

The focus in this latter case is then on knowledge mining, knowledge representation and semantic alignment within the documents themselves. 

 

Also typically these documents can be sent in support of transactional XML - e.g. as in with a Grant Application Submission - you have the transactional XML that contains details of the submitting organization, budget, duration and fixed content items, and then attached are supporting PDF documents - letters of recommendation, project definition and approach, prior related work, published work, facilitaties, and so on.

 

So - I believe you are discussing formalizing mechanisms for the latter - PDF, xdoc, odp and other rich document formats using XML?

 

Thanks, DW

"The way to be is to do" - Confucius (551-472 B.C.)