adasal wrote:
> Joachim what are your thoughts on OWL export of the object model? Where
> would that be used?
>
The main use for me is for documentation purposes. It is very practical
to take the owl model, import that into protégé and use the Jambalaya
plugin to create a graphical representation of the entities and the
links between them.
While I had hoped this would also be possible by experting the model in
UML (using the xmi format), it seems this does not allow storing a
graphical representation (at least not in the tools I looked at).
> I have to admit I am interested in something else, but have made no
> progress, that of the possible use of Tapestry with OWL. Henry Story has the
> story (excuse the pun). https://sommer.dev.java.net/sommer.html
> It seems to me that if you have implemented the export of the object model
> into OWL that is a step away from consuming OWL within Tapestry perhaps by
> creating a pipeline?
>
To a large extent, you could also do the reverse mapping, converting owl
into a equanda domain model and this can then be used to build the
persistence layer and user interface. The difference being that owl is
more generic in (data) modelling capabilities but the domain model has
specific features to add annotations about constraints and hints for the
user interface.
> Might this have some benefit? Henry Story discuses ActiveRDF extension to
> Ruby where using RDF seems as natural as importing a package. I think it
> would have benefits. Display data according to inferred type and so on.
> What do you think?
>
In the equanda context, you have to keep in mind that it uses code
generation, and thus a compilation step is necessary to move from model
(be it owl or equanda's own representation) to a running program. At
first guess this seems to be a constraint.
Apart from that, I think I need a better understanding of what you want
to achieve to give proper feedback.
Kind regards,
Joachim
--
Joachim Van der Auwera
PROGS bvba, progs.be

-------- Original Message --------
Subject: Re: [ANN] equanda 0.9 released
Date: Fri, 9 May 2008 19:04:06 +0100
From: adasal <adam.saltiel@...>
Reply-To: Tapestry users <users@...>
To: Tapestry users <users@...>
References: <481ECAA8.70806@...>
<e8aa138c0805070423q5d473akb8c743864cc024ca@...>
Joachim what are your thoughts on OWL export of the object model? Where
would that be used?
I have to admit I am interested in something else, but have made no
progress, that of the possible use of Tapestry with OWL. Henry Story has the
story (excuse the pun). https://sommer.dev.java.net/sommer.html
It seems to me that if you have implemented the export of the object model
into OWL that is a step away from consuming OWL within Tapestry perhaps by
creating a pipeline?
Might this have some benefit? Henry Story discuses ActiveRDF extension to
Ruby where using RDF seems as natural as importing a package. I think it
would have benefits. Display data according to inferred type and so on.
What do you think?
Adam
2008/5/7 adasal <adam.saltiel@...>:
> Hi Joachim,
> I have looked at your web site and discussed this with colleagues. It seems
> like a very interesting development to me. The apparent ease with which MVC
> can be split between different machines may be of particular interest to us
> due to the scale and further scaling needs of our web site, one of the
> largest UK web sites.
> We are not actively developing either with Tapestry or anything else at the
> moment for reasons too boring to go into here.
> But I am actively promoting Tapestry adoption, whether this turns out to be
> 4 or 5 will depend on time frames.
> Your tool is very welcome and increases the credibility of what is already
> a very credible framework.
> Adam Saltiel
> Java Enterprise Designer
> Serco Web Solutions
> Serco Plc
>
> 2008/5/5 Joachim Van der Auwera <joachim@...>:
>
> equanda, a open source project to generate a JEE application based on a
>> domain model, has released version 0.9.
>>
>> equanda generates the EJB3 access objects with possibility for powerful
>> declarative constraints and added programmatic constraints.
>> equanda also generates a tapestry5 based user interface with powerful
>> options for customizations.
>> All this (and quite a few other bots and pieces) are generated at compile
>> time from a XML description of the data and constraints. The customizations
>> remain intact in the generation process.
>>
>> This is the first useable release of equanda since the project started
>> (though the user interface still lacks features).
>>
>> Notable changes include :
>> - initial tapestry5 user interface
>> - type handling in field templates now also interprets subtags
>> - filter string per table
>> - improved form traversal in user interface, which also auto switches to
>> the next tab
>> - allow templates to define extra key-value pairs, possibly overwritten by
>> user
>> - fields named "Reference" or "Description" should automatically be marked
>> as is-reference or is-description
>> - generate UML and OWL from the domain model
>> - Improve xml reading/handling in domain model parsing code
>> - add selectors on proxies
>> - create archetype for empty equanda project
>> - tapestry5 accordion component
>> - tapestry5 tabs component
>> - tapestry5 FormTraversal component
>> - add equandaReset() method in proxies to revert the state to the database
>> values
>> - tapestry5 create "manifest" binding prefix
>> - Should allow a table type (in the inheritance tree) to be impossible to
>> create
>>
>> For more information, visit the project web site : http:// equanda.org/
>>
>> --
>> Joachim Van der Auwera
>> http://blog.progs.be/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
--
Joachim Van der Auwera
PROGS bvba, progs.be

equanda, a open source project to generate a JEE application based on a
domain model, has released version 0.9.
equanda generates the EJB3 access objects with possibility for powerful
declarative constraints and added programmatic constraints.
equanda also generates a tapestry5 based user interface with powerful
options for customizations.
All this (and quite a few other bots and pieces) are generated at
compile time from a XML description of the data and constraints. The
customizations remain intact in the generation process.
This is the first useable release of equanda since the project started
(though the user interface still lacks features).
Notable changes include :
- initial tapestry5 user interface
- type handling in field templates now also interprets subtags
- filter sttring per table
- improved form traversal in user interface, which also auto switches to
the next tab
- allow templates to define extra key-value pairs, possibly overwritten
by user
- fields named "Reference" or "Description" should automatically be
marked as is-reference or is-description
- generate UML and OWL from the domain model
- Improve xml reading/handling in domain model parsing code
- add selectors on proxies
- create archetype for empty equanda project
- tapestry5 accordion component
- tapestry5 tabs component
- tapestry5 FormTraversal component
- add equandaReset() method in proxies to revert the state to the
database values
- tapestry5 create "manifest" binding prefix
- Should allow a table type (in the inheritance tree) to be impossible
to create
For more information, visit the project web site : http://equanda.org/
<http://sourceforge.net/projects/equanda&gt;
--
Joachim Van der Auwera
http://blog.progs.be

equanda-tapestry5, the library of tapestry5 components which are
independent from the rest of the equanda framework, had an intermediate
version 0.8.5.
Considering that this had no version history, was not reproducable and
(in hindsight) contained some problems, this version has been removed
from the repository now that equanda 0.9 has been released.
If you were using 0.8.5 then you should update your pom.
Sorry for the inconvencience,
Joachim
--
Joachim Van der Auwera
blog.progs.be