[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Compound processing

• To: xml-dev@l...
• Subject: Re: Compound processing
• From: Gavin Thomas Nicol <gtn@r...>
• Date: Wed, 23 Jan 2002 14:48:14 -0500
• In-reply-to: <200201231842.NAA10220@m...>
• Organization: Red Bridge Interactive, Inc.
• References: <200201231842.NAA10220@m...>

On Wednesday 23 January 2002 01:42 pm, Mark Baker wrote:
> Ditto for every other task.  A compound editor could activate an SVG
> editor in-place within a WYSIWYG XHTML editor.  A compound
> compressor could activate compressors optimized for each namespace,
> yielding superior compression.  etc..

Sounds like Fresco/OpenDoc/ActiveX et al. The "document-centric" 
approach to computing much favored by Tog et al. Very nice for 
presentation and for object reuse.

One of the problems with this is approach is the coordination between 
different elements. Something has to organize these things into a 
coherent whole.... the summarizer case you gave illustrates this 
point. If the XHTML summarizer doesn't understand the SVG summarizer, 
you may not get an accurate summary (for example, perhaps the XHTML 
says "Be nice!" and the SVG says, in big bold letters "Go away".

Point being that while component-level processing is useful, you still 
need to be able to manipulate the document as a whole too... they are 
not equivalent.

• References:
  • Compound processing
    • From: Mark Baker <distobj@a...>

• Prev by Date: Re: Strategies for a lowly XML document
• Next by Date: Re: Strategies for a lowly XML document
• Previous by thread: Re: Compound processing
• Next by thread: Re: Compound processing
• Index(es):
  • Date
  • Thread