Hello,
We've been extremely happy with your documentation and Holger's blog.
SPIN, SPARQLMotion, Ensemble,... were totally unknown and in a short
laps of time we could get the essence in the fingers. Of course
without being specialists.
Most doubts about the procedures we have is on the Ensemble part.
We would like to bring a first module from ontology-development level
to the application level.
Before doing that, we have a few requests for clarification where in
doubt.
The fact is that either solution might require some significant work.
1.Is it so that the SPIN-functions determined in TBC will not be
ported to Ensemble in the foreseeable future (next few releases) ?
2.Most restrictions we declare in TBC are cardinality restrictions.
If we port them to TBE via the SPARQLMotion module, starting from the
assumption we have a number of forms with 20 or more properties, can
we still use “selectedResource” as input for the cardinality check or
should we define the cardinality check with each property separately
for the form ?
We would end up with 20 X 2 (min and max cardinality found in function
modules) to be executed for any single form in that case.
3.Is there any plan to link the SPIN-check on the cardinality
restrictions to the owl-properties?
The idea would be to determine in owl the min, max or exact number of
properties with a reference from the SPIN-function to the owl-
property.
<owl:Restriction>
<owl:onProperty rdf:resource="parties#hasName"/>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/
XMLSchema#int"
>1</owl:cardinality>
</owl:Restriction>
Perhaps there is already now a way to refer to that property but we
don't know how to perform this.
We have 2 questions about the form module in TBE.
1.The lay-out is very well taken from the defined forms in TBC for the
class.
However, we would like to have standard an empty text box or combo box
if applicable for the properties. This is OK in TBC but the settings
are not copied to TBE.
2.Concerning the object properties, there are the 2 options: “create
new” or add existing entry”. Is it possible to hide the option “create
new” when needed ? When the property refers to the value partition it
is namely unlikely that a normal user is allowed to adapt the
referential values.
We do not want to bother you with research work, please do not
hesitate to refer to sources already treating the subject.
Thank you in beforehand
Kind regards
Eddy Vanderlinden
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TopBraid Composer Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-composer-users?hl=en
-~----------~----~----~----~------~----~------~--~---
