Hi Peter,
personally I prefer to reduce the dependencies of my ecosystem using
"popular" tool like XML[1] , OWL[2] and sparql[3].

Probably it is reinventing (again) the wheel*,* but for my proposes I want
to follow the W3C standards.

Regards,
Fabrizio

[1]http://www.w3.org/standards/xml/
[2] http://www.w3.org/standards/techs/owl
[3] http://www.w3.org/standards/semanticweb/query.html

On Sat, Sep 21, 2013 at 11:31 PM, Peter Soetens <peter [..] ...>wrote:

> Hi Fabrizio,
>
> On Mon, Sep 16, 2013 at 2:34 PM, Fabrizio Boriero
> <fabrizio [dot] boriero [..] ...> wrote:
> > Hi all,
> > I want to invite you to test and contribute to develop this script that
> > generates Orocos components.
> >
> > https://bitbucket.org/fabrizio_boriero/oromodel
> >
> > It is a modified version of "orocreate-pkg" that allow to define an xml
> > model of component and use it to generate the "skeleton" code
> (input/output
> > ports, properties and ports datatype).
> >
> > The next step, is to implement the possibility to query an OWL database
> so
> > is possible to generate components from a web-based ontology.
>
> So it's doing something that orogen is doing (in a ruby dsl instead of
> xml).
>
> It might have been easier to have something that converts to the ruby
> dsl and then let orogen generate the remainder of the code.
>
> Peter
>