SOX

[Graham Moore]

>I see two distinct things here:
>    1. Serialization
>   2. Document processing.

I think that serialisation is a part of an object system. We are dealing 
with object systems that can be - potentially - viewed through multiple 
functional lenses. To enable this we've decided upon a standard way to 
serialise and instantiate instances - XML and domBuilders.

>When processing a document, the application should decide on
>the classes to be used depending on (a) the markup language
>of the document and (b) how the document is to be processed.

I agree. Although I dont think we should think of processing documents. We 
should view it more generally as invoking operations on an object model.

>For serialization, the mapping should be specified in the
>document.

The elementNode would / should provide the XML serialisation, any further 
serialisation formats are implemented in the functional mixins, as are the 
application specific methods. The application will serialise the structure 
as and when it needs to. If I'm sending my object model to an XML aware 
process then i'll use the elementNode serialiseXML method, if I'm sending it 
 as the response to a request for a web page then I'll call the mixed-in 
serialiseHTML method.

>> But we should be able to mix these.

A  delegation model would support the dynamic inclusion and reconfiguration 
of the functionality of a given instance. Thus providing multiple functional 
mixins and multiple mixin configurations.

graham.

gdm at dpsl.co.uk




xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)