Hi Chris, On Tue, Jan 29, 2019 at 8:26 AM Christofer Dutz <christofer.d...@c-ware.de> wrote: > > Hi all, > > I am a member of the Apache PLC4X podling. There we are implementing drivers > for communicating with industrial hardware. > Now we had started with manually implemented Java drivers, but it has always > been our goal to ship drivers in multiple languages. > > As we are currently starting work on the C++ versions, it was time to work on > some way to universally define these protocols > and have the drivers in each supported language generated. > > As a first step I wrote DFDL schemas and tests using Apache Daffodil and this > worked perfectly for defining the format of the > messages being exchanged. Now I still had to model the protocol itself: Which > message with what content is sent at which time? > How does the information provided by users get in requests and out of > responses? > So I was looking for some way to specify a State machine in XML … I stumbled > over SCXML > And can you imagine my surprise when I noticed Apache has something for this > in its toolbox? > > Right now I’m working on writing such a SCXML schema mixing together SCXML + > DFDL + Custom extensions to achieve the > goal of fully specifying these protocols. So far it’s looking good, but I > would like to ask, if someone here (ideally with SCXML experience) > would be interested in joining us and working on this.
Sounds cool! I'm not familiar with DFDL, but I'd like to help with some of my experiences with SCXML and our current Commons SCXML implementations. > > I know that the activity on the SCXML project seems to have been … well > minimal. But still I think it’s a good option. > > Any opinions, suggestions, things I should consider? One issue with the SCXML subproject is that it has been refactored a lot since v2, but it has never been released for years. So, people seem to feel hard to try it. Another is that Ate and I have used it mostly for a specific use case--document publication workflow in CMS--with M1 [1]; it kind of lacks of diversity. In that sense, new faces from diverse backgrounds will be more than welcome and more beneficial to the community. Perhaps you can test some PoC or its scenarios in conceptual level with M1 tag to see if everything is okay. Another thing is that we should consider releasing it often (again like 0.x's). Perhaps just because we bumped the version to 2.0.0 thanks to the expected whole refactoring, we might just have been hesitant to cut a release of v2.x.x while we're not ready yet to fulfill all the requirements of SCXML specification. Regards, Woonsan [1] http://commons.apache.org/proper/commons-scxml/roadmap.html > > Chris --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
