We had a bug related to this in 3.4.0 which is fixed in 3.4.1. Please correct the namespace of "spin" manually - it did not include the # at the end. And once you are at it, please upgrade to 3.4.1 to avoid this problem in the future.
Thanks & apologies for the inconvenience Holger On Feb 11, 2011, at 8:44 AM, John Perdoni wrote: > Scott, thank you for the continued help. > > All seems ok as far as having spin:contstraints available, the rules > are created in the same file and I had no propblem seeing the > violations from the kennedy file. > > I do see however that if i try and create a new constraint in the > affected files, I get a red squiglly lines under the predicates in the > sparql expression box, which I presume to mean that the namespace is > not recognised > > Below is the code for the imports and the code for one class that > constraints built on it. I have not got a clue where the prefix j:0 > has come from, surely this should be spin > > <owl:Ontology rdf:about="http://cortext.net/library/publishedBook/ > codeOfPractice_3rd_Edition"> > <owl:imports rdf:resource="http://cortext.net/library/coreModel"/> > <owl:imports rdf:resource="http://cortext.net/library/ > publishedBooks"/> > <owl:versionInfo rdf:datatype="http://www.w3.org/2001/ > XMLSchema#string" >> Created with TopBraid Composer</owl:versionInfo> > <j.0:imports rdf:resource="http://topbraid.org/spin/rdfsplus"/> > </owl:Ontology> > > > <owl:Class rdf:about="http://cortext.net/library/publishedBook/ > codeOfPractice_3rd_Edition#Page"> > <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"; >> Page</rdfs:label> > <rdfs:subClassOf rdf:resource="http://www.w3.org/2002/07/ > owl#Thing"/> > <j.0:constraint> > <spl:Attribute> > <rdfs:comment rdf:datatype="http://www.w3.org/2001/ > XMLSchema#string" >> the paragraphs this page contains</rdfs:comment> > <spl:minCount rdf:datatype="http://www.w3.org/2001/ > XMLSchema#integer" >> 1</spl:minCount> > <spl:predicate rdf:resource="http://cortext.net/library/ > coreModel#hasChildParagraph"/> > </spl:Attribute> > </j.0:constraint> > <j.0:constraint> > <spl:Attribute> > <rdfs:comment rdf:datatype="http://www.w3.org/2001/ > XMLSchema#string" >> the page number of this page</rdfs:comment> > <spl:maxCount rdf:datatype="http://www.w3.org/2001/ > XMLSchema#integer" >> 1</spl:maxCount> > <spl:minCount rdf:datatype="http://www.w3.org/2001/ > XMLSchema#integer" >> 1</spl:minCount> > <spl:predicate rdf:resource="http://cortext.net/library/ > coreModel#pageNumber"/> > </spl:Attribute> > </j.0:constraint> > <j.0:constraint> > <spl:Attribute> > <rdfs:comment rdf:datatype="http://www.w3.org/2001/ > XMLSchema#string" >> the type of page either default or override. </rdfs:comment> > <spl:defaultValue rdf:datatype="http://www.w3.org/2001/ > XMLSchema#string" >> default</spl:defaultValue> > <spl:maxCount rdf:datatype="http://www.w3.org/2001/ > XMLSchema#integer" >> 1</spl:maxCount> > <spl:minCount rdf:datatype="http://www.w3.org/2001/ > XMLSchema#integer" >> 1</spl:minCount> > <spl:predicate rdf:resource="http://cortext.net/library/ > coreModel#pageType"/> > </spl:Attribute> > </j.0:constraint> > <j.0:constraint> > <spl:Attribute> > <rdfs:comment rdf:datatype="http://www.w3.org/2001/ > XMLSchema#string" >> The Published Book of which this page is obtained from</ > rdfs:comment> > <spl:defaultValue rdf:resource="http://cortext.net/library/ > publishedBooks#IEE_Code_of_Practice_3rd_Edition"/> > <spl:maxCount rdf:datatype="http://www.w3.org/2001/ > XMLSchema#integer" >> 1</spl:maxCount> > <spl:minCount rdf:datatype="http://www.w3.org/2001/ > XMLSchema#integer" >> 1</spl:minCount> > <spl:predicate rdf:resource="http://cortext.net/library/ > coreModel#source"/> > </spl:Attribute> > </j.0:constraint> > <j.0:constructor> > <spl:ConstructDefaultValues/> > </j.0:constructor> > </owl:Class> > > > On Feb 10, 10:20 pm, Scott Henninger <[email protected]> > wrote: >> John, yes, the import is required, but does not have to be direct. It >> can be an import for an imported file. As long as the >> spin:constraints property is available, you should be OK. In >> particular your scenario should work, so we may need more details on >> what is occurring. >> >> Also make sure the rules are defined in the currently selected model. >> To check this, choose the property spin:constraints so it appears in >> the form and use Find references (the down arrow in the top icon row >> for Composer, or use Resource > Find reference in the menu). >> >> As a common check, create a new file and import kennedysSPIN.rdf. >> Turn on constraint violation warnings and you will see two violation >> warnings in the Problems view. The pre-defined data problem is >> that :StephenSmith's gender is incorrect, causing a constraint >> violation warning that you can also see if you choose :StephenSmith >> for display in the form. >> >> -- Scott >> >> P.S. I would suggest using .ttl instead of .n3 - another story for >> another day. >> >> On Feb 10, 4:03 pm, John Perdoni <[email protected]> wrote: >> >> >> >>> Scott thanks for the reply, I am aware of how to switch on the >>> checking using the triangle and how to use the refresh and problems >>> view. However my problem is that in two of my .n3 files it does not >>> work, yet if these models are imported into another file the rules >>> work. >> >>> I am trying to keep my imports down to a mininum, do I need to have >>> the spin namespace imported into every file. >> >>> I have also noticed that after taking the steps listed previously I >>> have ended up with the following import into one of the affected >>> files >> >>> <j.0:imports rdf:resource="http://topbraid.org/spin/rdfsplus"/> >> >>> On Feb 10, 9:51 pm, Scott Henninger <[email protected]> >>> wrote: >> >>>> John; A nice feature of SPIN is that constraint violation warnings are >>>> separate from inference through SPARQL rules. I.e. as opposed to OWL >>>> where only consistency checking is supported, you can write a >>>> constraint violation rule for anything that can be expressed in >>>> SPARQL. >> >>>> To turn on constraint violation warnings, click the yellow triangle in >>>> the top icon row in Composer. To view all constraint violations open >>>> the Problems view (Window > Show View > Problems) and click on the >>>> refresh button. This will check all rules defined in spin:constraint >>>> properties against all members of the class. A nice set of examples >>>> are found in the :Person class in the TopBraid/Examples/ >>>> kennedysSPIN.rdf file. >> >>>> -- Scott >> >>>> On Feb 10, 3:31 pm, John Perdoni <[email protected]> wrote: >> >>>>> Hi, for some reason or another the spin constraint violations and >>>>> refresh seem to have stopped working. I will try and explain what I >>>>> was doing leading up to this issue, it may shed some light. >> >>>>> I was looking at some inverse functional properties and set one up, >>>>> pressed the inference play button and recieved and error saying (from >>>>> my memory) something like, no rules found, you may want to check the >>>>> profile tab for owl-rl. I found the tab and clicked the checkbox for >>>>> owl-rl, running inferences is fine now, but the constraint violations >>>>> have stopped working. >> >>>>> I have reset to the following >> >>>>> Under the inference tab I have the following setup >> >>>>> Input:Asserted Triples >>>>> | >>>>> TopSpin (sparql Rules) >>>>> non-incremental, iteratively) >>>>> | >>>>> Output :Infrerred Triples >> >>>>> The ontology profile tab has nothing checked. >> >>>>> If possible can you shed some light on the issue. >> >>>>> thanks in advance >> >>>>> John- Hide quoted text - >> >>>> - Show quoted text -- Hide quoted text - >> >> - Show quoted text - > > -- > You received this message because you are subscribed to the Google > Group "TopBraid Suite Users", the topics of which include TopBraid Composer, > TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. > 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-users?hl=en -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. 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-users?hl=en
