Barb,

yes, spl:Attribute is a constraint like any other (assuming it is used  
as spin:constraint in the RDF model that is the input to the module).  
The new module sml:CheckConstraints will then also report violations  
of it.

Holger


On Sep 8, 2009, at 8:12 AM, Barb wrote:

>
> Holger,
>
> You previously mentioned that there's currently no clean mechanism to
> perform constraint checking in SPARQLMotion.
>
> I'm currently having issues validating an spl:attribute, which is also
> a constraint.
>
> Would this be part of that "no clean mechanism" list?
>
> If so, will it be included in the sml:CheckConstraints for 3.2 ?
>
> Barb
>
> On Sep 4, 9:54 am, Catrina <[email protected]> wrote:
>> Great, thanks.  Looking forward to release 3.2.
>>
>> ~Catrina
>>
>> On Sep 3, 6:33 pm, Holger Knublauch <[email protected]> wrote:
>>
>>
>>
>>> FYI I have added a new SPARQLMotion module sml:CheckConstraints  
>>> for 3.2
>>
>>> Holger
>>
>>> On Sep 3, 2009, at 9:27 AM, Holger Knublauch wrote:
>>
>>>> Hi Catrina,
>>
>>>> no there is currently no clean mechanism to perform constraint
>>>> checking in SPARQLMotion. I will add this to the feature requests
>>>> list.
>>
>>>> However, if your constraint checks are of the CONSTRUCT form (i.e.
>>>> constructing spin:ConstraintViolations), then you can use
>>>> sml:ApplyTopSPIN if you declare
>>
>>>>    spin:constraint rdfs:subPropertyOf spin:rule .
>>
>>>> Holger
>>
>>>> On Sep 3, 2009, at 9:12 AM, Catrina wrote:
>>
>>>>> I have a class that has a spin:constraint defined and I'd like to
>>>>> have
>>>>> this constraint checked from within a SPARQLMotion script.  Note  
>>>>> that
>>>>> my SPARQLMotion script and my class definition reside in two  
>>>>> separate
>>>>> files.
>>
>>>>> An instance of class is created with an ApplyConstruct module  
>>>>> within
>>>>> my script.  Is there a way to verify that none of the class's
>>>>> spin:constraints were violated?
>>
>>>>> My class defintion and spin:constraint look similar to the
>>>>> kennedy:Person example on the following web page (see the first
>>>>> screenshot under Constraint Checking subtitle with the age value
>>>>> constraint):
>>>>> http://topquadrant.com/products/SPIN.html
>>
>>>>> As I mentioned my script creates an instance of my class with an
>>>>> ApplyConstruct module.  Then, I thought I could use an  
>>>>> ApplyTopSPIN
>>>>> module to perform constraint checking.  So I created an  
>>>>> ApplyTopSPIN
>>>>> module and added spin:constraint to the sml:predicate of this  
>>>>> module.
>>>>> Then, I send my constructed triples to this ApplyTopSPIN module.
>>
>>>>> When I execute my script, I do not see any messages stating a
>>>>> spin:constraint violation occurred.  The error log contains a  
>>>>> message
>>>>> stating "TopSPIN took 0 ms for 0 queries".  So it doesn't appear  
>>>>> that
>>>>> the check was even made.
>>
>>>>> Should I be able to use ApplyTopSPIN for such usage?  Are there  
>>>>> any
>>>>> other suggestions on how to perform constraint checking from  
>>>>> within a
>>>>> SPARQLMotion script?
>>
>>>>> Do I need to import spinowl.owl or spinrdfs.owl?
>>
>>>>> Thanks,
>>>>> Catrina- Hide quoted text -
>>
>>> - Show quoted text -- Hide quoted text -
>>
>> - Show quoted text -
> >


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to