Namespace prefixes, right? Yes, this is intended behavior. The
underlying issue is that qnames are not necessarily unique. Since the
prefix can be defined in imported files, there isn't a good way to
control what the prefixes expand to.
Suppose you import a file that defines a prefix xyz as
Jody,
I have just added a new property function called tops:for that will
help with such iterations. The syntax would be (in an
sml:IterateOverSelect)
sml:selectQuery = SELECT ?index WHERE { ?index tops:for (1 10) }
to have the body of the loop repeated with ?index = [1..10] as input.
The
> Seems to say spl:Argument or spl:Attribute can be attached as a
> spin:constraint, and I don't think either of them are either ASK or
> CONSTRUCT queries. Perhaps I'm getting lost in the meta levels?
Both spl:Argument and spl:Attribute are SPIN templates that wrap ASK
queries. So substitu
Here's what I think happened. At one point I created a copy of your spin.owl
ontology so I could edit it for our purposes (ostensibly to use it without
using your sp.owl ontology since I was just going to use text representations
of the SPARQL Queries themselves), and gave it a URL of
http://
Jeff; Exactly how was it defined twice? The same prefix to different
URIs or the same namespace to different prefixes? Just trying to get
an idea of what happened.
A couple of additional notes. In general a SPARQL query that matches
a bnode will return the bnode. Some are recognized by Compo
Still struggling a little. The comment for spin:constraint states:
Links a class with constraints on its instances. The values of this
property are "axioms" expressed as CONSTRUCT or ASK queries where the
variable ?this refers to the instances of the surrounding class. ASK
queries must evaluate t
Jeff,
I don't know but it seems to work fine for me. I have tried it on the
KennedySPIN ontology that comes as part of the beta. Then, when I run
SELECT ?frConstraint
WHERE {
kennedys:Person spin:constraint ?frConstraint .
}
I correctly get two constraints, even though they are blank nodes
Hi Jeff,
spin:constructor can be used to add arbitrary triples to new objects
when they are created.
The particular template spl:ConstructDefaultValues is meant to be used
in conjunction with spl:Argument or spl:Attribute: It will look at any
defined default values for those arguments or at
Ah yes, this is a typo in the comment. Indeed, spin:query should be
used. Thanks for reporting it!
Note that for backward compatibility, the values of sparql:query are
still entered and stored as strings, but technically it has been made
a sub-property of spin:query. Also for backward compa
Funny, but this doesn't work either (I get no results):
SELECT ?prop ?frConstraint
WHERE {
Neutral:FailureRate ?prop ?frConstraint .
FILTER (?prop = spin:constraint)
}
-Original Message-
From: Schmitz, Jeffrey A
Sent: Wednesday, January 07, 2009 12:54 PM
To: topbraid-composer-u
Using TBC 3.0 beta, I have a class (Neutral:FailureRate) that I've
attached a spin:constraint to. When I try to query for the constraint
from the SPARQL tab with:
SELECT ?frConstraint
WHERE {
Neutral:FailureRate spin:constraint ?frConstraint .
}
I get no result. However, when I use:
SELEC
Looking in the spl.owl ontology I'm a little confused about the
slp:ConstructDefaultValues Template Class. It states:
This template can be attached as spin:constructor to a root class such
as rdfs:Resource to ensure that SPIN processors assign default values to
certain properties. Looks for any
I'm trying to update to the new versions of the TBC sparql.owl ontology
and noticed this comment attached to the sparql:query property:
Deprecated: please use sp:query instead.
However, I don't see a sp:query property in the sp.owl ontology. Should
this comment reference the spin:query propert
Thanks Holger,
I completely understand. I just wanted to ask before I possibly
headed down the road of re-implementing it here.
Jeff
-Original Message-
From: Holger Knublauch [mailto:hol...@topquadrant.com]
Sent: Tuesday, January 06, 2009 5:56 PM
To: topbraid-composer-users@googlegr
14 matches
Mail list logo
