Re: [topbraid-users] general constraint checking 'library'?

[Jack Hodges]

Thank you Holger. I was not aware that the spl had so many 
constraint-related functions. I tend to look in the SPARQL Functions 
Reference for available functions. In my SPIN file I see imports for spin, 
spinx, and sp, but not for spl. On the spinrdf.org/spl/spl.html there is a 
reference to spinrdf.org/spl but I am not seeing any comprehensive 
documentation. So as much as I appreciate your response and clarification, 
how would I have found this on my own?

I would love to play with SHACL but the TQ comments about SHACL 
implementation in Topbraid say things like 'not even close to production 
ready' so I've been waiting...but waiting with great anticipation 
nonetheless.

Jack

On Tuesday, June 7, 2016 at 5:15:11 PM UTC-7, Holger Knublauch wrote:
>
> Hi Jack,
>
> in SPIN we have the SPL library that is supposed to contain "standard" 
> constraint types as SPIN templates. Right now it includes:
>
> spl:CountPropertyConstraintTemplates
> spl:ExistencePropertyPairConstraint
> spl:LessThanOtherPropertyPairConstraint
> spl:NonExistencePropertyPairConstraint
> spl:ObjectCountPropertyConstraint
> spl:PrimaryKeyPropertyConstraint
> spl:PropertyConstraintTemplates
> spl:PropertyPairConstraintTemplates
> spl:RangePropertyConstraint
> spl:RegexPropertyConstraint
> spl:StringLengthPropertyConstraint
> spl:TypePropertyConstraint
> spl:UniquePropertyValueConstraint
> spl:UntypedObjectPropertyConstraint
>
> Other than that, I would recommend looking into SHACL, which will have 
> more support in TopBraid 5.2. Although it is still evolving it will have 
> the advantage of being a W3C standard.
>
> http://w3c.github.io/data-shapes/shacl/
>
> HTH
> Holger
>
>
> On 8/06/2016 7:39, Jack Hodges wrote:
>
> Topbraid Composer has several SPIN functions that are pretty specific to 
> defining constraints for model testing. Examples are spl:instanceOf, 
> spl:hasValueOfType, smf:definedIn, smf:min/maxCardinality, smf:qname, 
> spif:localName, spin:constructViolations, spin:violatesConstraints, etc. It 
> seems clear that some effort has been expended to create functions that 
> could be used in a generic constraints 'library' (i.e., to validate type, 
> cardinality, value, threshold, range, ...), but does such a library of SPIN 
> functions and ASK templates already exist? I hate to reinvent the wheel... 
>
> Jack
> -- 
> You received this message because you are subscribed to the Google Group 
> "TopBraid Suite Users", the topics of which include the TopBraid Suite 
> family of products and its base technologies such as SPARQLMotion, SPARQL 
> Web Pages and SPIN.
> To post to this group, send email to topbrai...@googlegroups.com 
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "TopBraid Suite Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to topbraid-user...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Group 
"TopBraid Suite Users", the topics of which include the TopBraid Suite family 
of products and its base technologies such as SPARQLMotion, SPARQL Web Pages 
and SPIN.
To post to this group, send email to topbraid-users@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to topbraid-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [topbraid-users] general constraint checking 'library'?

[Irene Polikoff]

Jack,

All spl functions are listed in the SPARQL Functions Reference.

Regards,

Irene Polikoff


From:  Jack Hodges 
Reply-To:  
Date:  Wednesday, June 8, 2016 at 12:04 PM
To:  TopBraid Suite Users 
Subject:  Re: [topbraid-users] general constraint checking 'library'?

Thank you Holger. I was not aware that the spl had so many
constraint-related functions. I tend to look in the SPARQL Functions
Reference for available functions. In my SPIN file I see imports for spin,
spinx, and sp, but not for spl. On the spinrdf.org/spl/spl.html there is a
reference to spinrdf.org/spl but I am not seeing any comprehensive
documentation. So as much as I appreciate your response and clarification,
how would I have found this on my own?

I would love to play with SHACL but the TQ comments about SHACL
implementation in Topbraid say things like 'not even close to production
ready' so I've been waiting...but waiting with great anticipation
nonetheless.

Jack

On Tuesday, June 7, 2016 at 5:15:11 PM UTC-7, Holger Knublauch wrote:
> 
>  Hi Jack,
>  
>  in SPIN we have the SPL library that is supposed to contain "standard"
> constraint types as SPIN templates. Right now it includes:
>  
>  spl:CountPropertyConstraintTemplates
>  spl:ExistencePropertyPairConstraint
>  spl:LessThanOtherPropertyPairConstraint
>  spl:NonExistencePropertyPairConstraint
>  spl:ObjectCountPropertyConstraint
>  spl:PrimaryKeyPropertyConstraint
>  spl:PropertyConstraintTemplates
>  spl:PropertyPairConstraintTemplates
>  spl:RangePropertyConstraint
>  spl:RegexPropertyConstraint
>  spl:StringLengthPropertyConstraint
>  spl:TypePropertyConstraint
>  spl:UniquePropertyValueConstraint
>  spl:UntypedObjectPropertyConstraint
>  
>  Other than that, I would recommend looking into SHACL, which will have more
> support in TopBraid 5.2. Although it is still evolving it will have the
> advantage of being a W3C standard.
>  
>  http://w3c.github.io/data-shapes/shacl/
>  
>  HTH
>  Holger
>  
>  
>  
> On 8/06/2016 7:39, Jack Hodges wrote:
>  
>  
>>  
>> Topbraid Composer has several SPIN functions that are pretty specific to
>> defining constraints for model testing. Examples are spl:instanceOf,
>> spl:hasValueOfType, smf:definedIn, smf:min/maxCardinality, smf:qname,
>> spif:localName, spin:constructViolations, spin:violatesConstraints, etc. It
>> seems clear that some effort has been expended to create functions that could
>> be used in a generic constraints 'library' (i.e., to validate type,
>> cardinality, value, threshold, range, ...), but does such a library of SPIN
>> functions and ASK templates already exist? I hate to reinvent the wheel...
>> 
>>  
>>  
>> Jack
>>  
>>  -- 
>>  You received this message because you are subscribed to the Google Group
>> "TopBraid Suite Users", the topics of which include the TopBraid Suite family
>> of products and its base technologies such as SPARQLMotion, SPARQL Web Pages
>> and SPIN.
>>  To post to this group, send email to topbrai...@googlegroups.com
>>  
>>  --- 
>>  You received this message because you are subscribed to the Google Groups
>> "TopBraid Suite Users" group.
>>  To unsubscribe from this group and stop receiving emails from it, send an
>> email to topbraid-user...@googlegroups.com  .
>>  For more options, visit https://groups.google.com/d/optout.
>>  
>  
>  
-- 
You received this message because you are subscribed to the Google Group
"TopBraid Suite Users", the topics of which include the TopBraid Suite
family of products and its base technologies such as SPARQLMotion, SPARQL
Web Pages and SPIN.
To post to this group, send email to topbraid-users@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to topbraid-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Group 
"TopBraid Suite Users", the topics of which include the TopBraid Suite family 
of products and its base technologies such as SPARQLMotion, SPARQL Web Pages 
and SPIN.
To post to this group, send email to topbraid-users@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to topbraid-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [topbraid-users] general constraint checking 'library'?

[Jack Hodges]

Hello Irene,

I mean no disrespect but are you sure? Here is the entire list of spl: 
functions from the SPARQL Functions Reference in the Topbraid Help (under 
Help->Contents->Topbraid Composer->Reference->SPARQL Functions Reference) 
for TBCME 5.1.3:

spl:hasArgument
spl:hasPrimaryKey
spl:hasValue
spl:hasValueOfType
spl:instanceOf
spl:isPrimaryKeyPropertyOfInstance
spl:isUntypedLiteral
spl:max
spl:min
spl:object
spl:objectCount
spl:objectInGraph
spl:objectSubProp
spl:primaryKeyProperty
spl:primaryKeyURIStart
spl:relevantPropertyAtClass
spl:subClassOf
spl:subPropertyOf
spl:subject
spl:subjectCount

and here are the items that Holger referenced this morning:

spl:CountPropertyConstraintTemplates

spl:ExistencePropertyPairConstraint

spl:LessThanOtherPropertyPairConstraint

spl:NonExistencePropertyPairConstraint

spl:ObjectCountPropertyConstraint

spl:PrimaryKeyPropertyConstraint

spl:PropertyConstraintTemplates

spl:PropertyPairConstraintTemplates

spl:RangePropertyConstraint

spl:RegexPropertyConstraint

spl:StringLengthPropertyConstraint

spl:TypePropertyConstraint


It looks to me as though the latter are class taxonomy categories, under 
which I would expect to see function instances, but I cannot see any of 
these categories in the Classes navigator. So the question remains of where 
they are and is there documentation for them?


Jack

On Wednesday, June 8, 2016 at 9:33:29 AM UTC-7, Irene Polikoff wrote:
>
> Jack,
>
> All spl functions are listed in the SPARQL Functions Reference.
>
> Regards,
>
> Irene Polikoff
>
>
> From: Jack Hodges >
> Reply-To: >
> Date: Wednesday, June 8, 2016 at 12:04 PM
> To: TopBraid Suite Users >
> Subject: Re: [topbraid-users] general constraint checking 'library'?
>
> Thank you Holger. I was not aware that the spl had so many 
> constraint-related functions. I tend to look in the SPARQL Functions 
> Reference for available functions. In my SPIN file I see imports for spin, 
> spinx, and sp, but not for spl. On the spinrdf.org/spl/spl.html there is 
> a reference to spinrdf.org/spl but I am not seeing any comprehensive 
> documentation. So as much as I appreciate your response and clarification, 
> how would I have found this on my own?
>
> I would love to play with SHACL but the TQ comments about SHACL 
> implementation in Topbraid say things like 'not even close to production 
> ready' so I've been waiting...but waiting with great anticipation 
> nonetheless.
>
> Jack
>
> On Tuesday, June 7, 2016 at 5:15:11 PM UTC-7, Holger Knublauch wrote:
>>
>> Hi Jack,
>>
>> in SPIN we have the SPL library that is supposed to contain "standard" 
>> constraint types as SPIN templates. Right now it includes:
>>
>> spl:CountPropertyConstraintTemplates
>> spl:ExistencePropertyPairConstraint
>> spl:LessThanOtherPropertyPairConstraint
>> spl:NonExistencePropertyPairConstraint
>> spl:ObjectCountPropertyConstraint
>> spl:PrimaryKeyPropertyConstraint
>> spl:PropertyConstraintTemplates
>> spl:PropertyPairConstraintTemplates
>> spl:RangePropertyConstraint
>> spl:RegexPropertyConstraint
>> spl:StringLengthPropertyConstraint
>> spl:TypePropertyConstraint
>> spl:UniquePropertyValueConstraint
>> spl:UntypedObjectPropertyConstraint
>>
>> Other than that, I would recommend looking into SHACL, which will have 
>> more support in TopBraid 5.2. Although it is still evolving it will have 
>> the advantage of being a W3C standard.
>>
>> http://w3c.github.io/data-shapes/shacl/
>>
>> HTH
>> Holger
>>
>>
>> On 8/06/2016 7:39, Jack Hodges wrote:
>>
>> Topbraid Composer has several SPIN functions that are pretty specific to 
>> defining constraints for model testing. Examples are spl:instanceOf, 
>> spl:hasValueOfType, smf:definedIn, smf:min/maxCardinality, smf:qname, 
>> spif:localName, spin:constructViolations, spin:violatesConstraints, etc. It 
>> seems clear that some effort has been expended to create functions that 
>> could be used in a generic constraints 'library' (i.e., to validate type, 
>> cardinality, value, threshold, range, ...), but does such a library of SPIN 
>> functions and ASK templates already exist? I hate to reinvent the wheel... 
>>
>> Jack
>> -- 
>> You received this message because you are subscribed to the Google Group 
>> "TopBraid Suite Users", the topics of which include the TopBraid Suite 
>> family of products and its base technologies such as SPARQLMotion, SPARQL 
>> Web Pages and SPIN.
>> To post to this group, send email to topbrai...@googlegroups.com
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "TopBraid Suite Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to topbraid-user...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> -- 
> You received this message because you are subscribed to the Google Group 
> "TopBraid Suite Users", the topics of which include the TopBraid Suite 
> family of products and its base technologies such as SPARQLMot

[topbraid-users] How to associate a constraint with a property?

[Jack Hodges]

I am building some constraints using ASK templates. In the myPurchases 
example when the checkInvoiceAge ASK template (an invoice with no paidDate 
is > 90 days old) is applied to the purchases:MaterialsPurchase class 
errors show up next to the invoiceDate and paidDate properties. I am 
guessing that this is because they are the only properties directly 
referenced in the checkInvoiceAge ASK template. Is this true?

And what if I want to associated a constraint test with a provided property 
name? How would I show the violation against that property? Right now it 
ends up showing against the instance, which isn't nearly as helpful.

Jack

-- 
You received this message because you are subscribed to the Google Group 
"TopBraid Suite Users", the topics of which include the TopBraid Suite family 
of products and its base technologies such as SPARQLMotion, SPARQL Web Pages 
and SPIN.
To post to this group, send email to topbraid-users@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to topbraid-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [topbraid-users] general constraint checking 'library'?

[Irene Polikoff]

Jack,

You are right. The items below are functions. The items Holger sent are
templates. I was simply saying that all functions that are shipped with TBC
models are listed in the reference page.

All templates are listed as well, but templates are web services so they are
documented in the administrative console  under the ³Available Web Services²
page in the TBL Administrator console.

These templates have been developed for use in our data governance products
­ EVN, RDM and EDG in order to allow business users specify data validation
rules in the web UI. For more details on how it is used and works see
http://www.topquadrant.com/docs/5.1/EVN-User-Guide_1802256.html#EVNUserGuide
-Addingconstraintstoaclass.

Thus, if you were running, for example, EVN this functionality would be very
apparent to you. Ways to create new constraint templates are described in
the Developer guide
http://www.topquadrant.com/docs/5.1/EVN-Developer-Guide_1802545.html#EVNDeve
loperGuide-GettingStartedwithCustomDataQualityRulesinEnterprise Vocabulary
Network 
 .

In short, they were not really created for TBC; thus, not documented in TBC
specific documentation.

Irene Polikoff


From:  Jack Hodges 
Reply-To:  
Date:  Wednesday, June 8, 2016 at 5:22 PM
To:  TopBraid Suite Users 
Subject:  Re: [topbraid-users] general constraint checking 'library'?

Hello Irene,

I mean no disrespect but are you sure? Here is the entire list of spl:
functions from the SPARQL Functions Reference in the Topbraid Help (under
Help->Contents->Topbraid Composer->Reference->SPARQL Functions Reference)
for TBCME 5.1.3:

spl:hasArgument
spl:hasPrimaryKey
spl:hasValue
spl:hasValueOfType
spl:instanceOf
spl:isPrimaryKeyPropertyOfInstance
spl:isUntypedLiteral
spl:max
spl:min
spl:object
spl:objectCount
spl:objectInGraph
spl:objectSubProp
spl:primaryKeyProperty
spl:primaryKeyURIStart
spl:relevantPropertyAtClass
spl:subClassOf
spl:subPropertyOf
spl:subject
spl:subjectCount

and here are the items that Holger referenced this morning:

spl:CountPropertyConstraintTemplates
spl:ExistencePropertyPairConstraint
spl:LessThanOtherPropertyPairConstraint
spl:NonExistencePropertyPairConstraint
spl:ObjectCountPropertyConstraint
spl:PrimaryKeyPropertyConstraint
spl:PropertyConstraintTemplates
spl:PropertyPairConstraintTemplates
spl:RangePropertyConstraint
spl:RegexPropertyConstraint
spl:StringLengthPropertyConstraint
spl:TypePropertyConstraint


It looks to me as though the latter are class taxonomy categories, under
which I would expect to see function instances, but I cannot see any of
these categories in the Classes navigator. So the question remains of where
they are and is there documentation for them?


Jack

On Wednesday, June 8, 2016 at 9:33:29 AM UTC-7, Irene Polikoff wrote:
> Jack,
> 
> All spl functions are listed in the SPARQL Functions Reference.
> 
> Regards,
> 
> Irene Polikoff
> 
> 
> From:  Jack Hodges  >
> Reply-To:   >
> Date:  Wednesday, June 8, 2016 at 12:04 PM
> To:  TopBraid Suite Users  >
> Subject:  Re: [topbraid-users] general constraint checking 'library'?
> 
> Thank you Holger. I was not aware that the spl had so many constraint-related
> functions. I tend to look in the SPARQL Functions Reference for available
> functions. In my SPIN file I see imports for spin, spinx, and sp, but not for
> spl. On the spinrdf.org/spl/spl.html   there
> is a reference to spinrdf.org/spl   but I am not
> seeing any comprehensive documentation. So as much as I appreciate your
> response and clarification, how would I have found this on my own?
> 
> I would love to play with SHACL but the TQ comments about SHACL implementation
> in Topbraid say things like 'not even close to production ready' so I've been
> waiting...but waiting with great anticipation nonetheless.
> 
> Jack
> 
> On Tuesday, June 7, 2016 at 5:15:11 PM UTC-7, Holger Knublauch wrote:
>> 
>>  Hi Jack,
>>  
>>  in SPIN we have the SPL library that is supposed to contain "standard"
>> constraint types as SPIN templates. Right now it includes:
>>  
>>  spl:CountPropertyConstraintTemplates
>>  spl:ExistencePropertyPairConstraint
>>  spl:LessThanOtherPropertyPairConstraint
>>  spl:NonExistencePropertyPairConstraint
>>  spl:ObjectCountPropertyConstraint
>>  spl:PrimaryKeyPropertyConstraint
>>  spl:PropertyConstraintTemplates
>>  spl:PropertyPairConstraintTemplates
>>  spl:RangePropertyConstraint
>>  spl:RegexPropertyConstraint
>>  spl:StringLengthPropertyConstraint
>>  spl:TypePropertyConstraint
>>  spl:UniquePropertyValueConstraint
>>  spl:UntypedObjectPropertyConstraint
>>  
>>  Other than that, I would recommend looking into SHACL, which will have more
>> support in TopBraid 5.2. Although it is still evolving it will have the
>> advantage of being a W3C standard.
>>  
>>  http://w3c.gi

Re: [topbraid-users] How to associate a constraint with a property?

[Irene Polikoff]

Violations from ASK templates always show against a resource that failed the
check. 

You can use CONSTRUCT templates. With these, you can create whatever
violation messages you want and define where it applies using
spin:violationPath property. This means that the violation can be shown for
some other resource, but I am not sure this is what you are asking for.


Irene Polikoff
From:  Jack Hodges 
Reply-To:  
Date:  Wednesday, June 8, 2016 at 5:28 PM
To:  TopBraid Suite Users 
Subject:  [topbraid-users] How to associate a constraint with a property?

I am building some constraints using ASK templates. In the myPurchases
example when the checkInvoiceAge ASK template (an invoice with no paidDate
is > 90 days old) is applied to the purchases:MaterialsPurchase class errors
show up next to the invoiceDate and paidDate properties. I am guessing that
this is because they are the only properties directly referenced in the
checkInvoiceAge ASK template. Is this true?

And what if I want to associated a constraint test with a provided property
name? How would I show the violation against that property? Right now it
ends up showing against the instance, which isn't nearly as helpful.

Jack
-- 
You received this message because you are subscribed to the Google Group
"TopBraid Suite Users", the topics of which include the TopBraid Suite
family of products and its base technologies such as SPARQLMotion, SPARQL
Web Pages and SPIN.
To post to this group, send email to topbraid-users@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to topbraid-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Group 
"TopBraid Suite Users", the topics of which include the TopBraid Suite family 
of products and its base technologies such as SPARQLMotion, SPARQL Web Pages 
and SPIN.
To post to this group, send email to topbraid-users@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to topbraid-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.