OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: XML Overlays and Deltas: Existing methods? Ideas?

Then I may be missing something vital in your 
application requirement.

A grove describes the exhaustive property set.   A grove 
plan can be the state of those given some application use 
or step in processing seen as the grove plan resulting from 
that step (simply, what is the property set after transform).  
As far as I can tell, changes in plans, packaging, etc. are 
functionally the same; different plans for groves.  

No AFAIK, it doesn't discuss transport mechanisms.  My 
question would be if the definitions are too heavy for 
the application of deltas.

Someone in the grove community should comment.  My 
preference would be if I am repackaging information 
to use XSLT definitions as long as the format remains XML.

Len Bullard
Intergraph Public Safety

Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h

-----Original Message-----
From: Joel Bender [mailto:jjb5@cornell.edu]

I think I understand that a grove is a collection of node classes and 
properties, and that the grove plan describes what the components are 
(and perhaps how they are encoded in some way, perhaps even an XML 
format).  That's about as far as I get.  My reading on groves hasn't 
found any place that describes how changes in plans are shipped 
around, nor can I find where changes in a grove as made by some 
application are packaged into a message that can be interpreted by 
another applications plan.