commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar" <>
Subject Re: [scxml] using schemas/xslt/xinclude to provide normalization
Date Fri, 02 Jun 2006 18:18:10 GMT
IMO, there is no denying that some of the things you list below add
value in terms of closing the loop for SCXML related development. In
Commons specifically, we tend to be vary of scope creep, so very
little of this, if at all any, will probably end up in Commons SCXML.

I believe there is a need for an additional community around SCXML,
which can be a little more accepting of the heterogeneous bits and
pieces that go into all facets of SCXML related development, from
Eclipse based editors and Rational plugins around state charts at the
modeling layer to various thin bridging APIs closer to many runtimes.
Perhaps if you are interested, and have some code to seed such a
project, it might be better to start a related project on sourceforge.
If you let me, I'd be happy to join in the fun there.


On 6/2/06, Nestor Urquiza <> wrote:
> Just in case the following steps help a little bit to
> fire some ideas ;-) I know this is not really and
> directly scxml related but since having a settings xml
> file holding all the configuration together with an
> scxml holding rules for behavior I feel like a
> necessity to have a too like this:
> 1)xml editor that shows in user friendly format (
> ideally web form ) a
> given xml file.
> 2)Allow xml chunk reuse. For example using XInclude or
> any other technique it should be able to handle an
> scenario of bookstores and libraries
> xml files that include books nodes which are uniques.
> If from one file
> a given book is updated the books.xml chunk should be
> updated and so appear updated in any single
> occurrence.
> 3)Be webdav aware to use it for distributed/concurrent
> edition.
> 4)Include Delta-V or any versioning system
> integration.
> --- Nestor Urquiza <> wrote:
> > Hello guys,
> > I have been thinking about different options to
> > provide xml normalization meaning I want to be able
> > to
> > maintain xml files or unique nodes with information
> > that is reused within a specific xml file (My
> > settings.xml file that is used from the datamodel
> > needs to reuse for different clients same nodes like
> > channels, offers and other entities). I gave it a
> > try
> > using xinclude but the parsers I have seen do not
> > implement xpointer() scheme but only the element()
> > scheme. On the other hand they do not provide way of
> > selecting fragments using xpath expressions as
> > XInclude propose thru #xpointer... included in the
> > href attribute. Using element() I am able to
> > maintain
> > individual files and include just the particular
> > nodes
> > I need in my final xml files, however I have to keep
> > the order of them because element works based on the
> > position of children like element(/1/2) to say use
> > the
> > second child from root.
> >
> > I was thinking about to use in the meanwhile (seems
> > like xerces will support the xpointer scheme and
> > even
> > an xpath scheme someday as well as jaxen as I read
> > from some dom4j postings) xslt to given the specific
> > nodes with ids just build the resulting xml file
> > where
> > the nodes are repeated and I can make my xpaths
> > simpler.
> >
> > In both cases above I heve always the worry about
> > the
> > maintanance of those several files that host unique
> > nodes and I am wondering if there is a better
> > solution.
> >
> > Still I think a better way has to exist and maybe
> > this
> > is using schemas. I hope some of you could give me
> > directions about where to look for a good solution.
> >
> > Thanks in advance
> > Nestor
> >

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message