[topbraid-users] RE: Support for editing undefined properties of property shapes (an node shapes)

Sorry: >>> It would be nice, though, if these at least show up under the group >>> “Undefined properties” (which they do not currently). They do show up now, probably a refresh-issue -Jan From: Jan Voskuil Sent: Tuesday, October 3, 2023 1:22 PM To: topbraid-users@google

[topbraid-users] Support for editing undefined properties of property shapes (an node shapes)

Hi, Just a small remark. When creating a property shape, we often need to add some extra triples with special properties due to self-imposed rules, for example: :MyClass-myProp a sh:PropertyShape ; rdfs:isDefinedBy ; … . The only way I can do this

[topbraid-users] owl2shacl

rdfs:domain are converted correctly. Best regards, -Jan Jan Voskuil | CEO Taxonic | Ontologist Veldzigt 2, 3454 PW, De Meern, The Netherlands T +31 (0)88 829 66 00 | M:+31 (0)6 14488335 jan.vosk...@taxonic.com<mailto:jan.vosk...@taxonic.com> | www.taxonic.com<http://www.taxonic.com/>

Re: [topbraid-users] superclass online

Hi Michel, Dereferencing is not an alternative to owl:import. Graph inclusion is a precisely defined mechanism, derefencing is not. As Berners-Lee put it in his famous (but “imperfect”) Linked Data paper, returning “useful information” when a resource URI is used as a URL is an expectation of be

RE: [topbraid-users] Proper use of sh:prefixes

Thanks Irene, very useful, -j From: topbraid-users@googlegroups.com On Behalf Of Irene Polikoff Sent: 01 June 2021 18:21 To: topbraid-users@googlegroups.com Subject: Re: [topbraid-users] Proper use of sh:prefixes On Jun 1, 2021, at 4:39 AM, Jan Voskuil mailto:jan.vosk...@taxonic.com

[topbraid-users] Proper use of sh:prefixes

yURI ; sh:prefix "skos" ; ] ; sh:declare [ sh:namespace http://www.wikidata.org/prop/direct/^^xsd:anyURI ; sh:prefix "wdt" ; ] ; . Jan Voskuil | CEO Taxonic Veldzigt 2, 3454 PW, De Meern, The Netherlands T +31 (0)88 829 66 00 | M:+31 (0)6 14488335 jan.

[topbraid-users] sh:maxCount set to zero

Hey, For a particular node shape I would like to make sure that instances of it do not have values for a particular property (but without closing the shape). So I wrote: ex:MyNode a rdfs:Class, sh:NodeShape ; sh:property [ sh:path ex:someProp ; sh:maxCount 0 ; ] . This is ignored

RE: [topbraid-users] skos question

Maybe [1] misses the owl:Ontology declaration, did you already try adding “, owl:Ontology” after “skos:ConceptScheme”? … -j a skos:ConceptScheme ; owl:imports ; From: 'Bohms, H.M. (Michel)' via TopBraid Suite Users Sent

RE: [topbraid-users] owl:oneOf to shacl ?

The shape is a property shape. Wherever the property in the property path occurs (i.e. ex:loadLevel), the constraint will be checked/validated. So, no need to specify sh:targetSubjectsOf --- unless you want the constraint to hold only if a specific type of subject is present. -j From: 'Bohms, H

RE: [topbraid-users] custom datatypes and SPARQL

Thanks, spif:cast and of course STRDT are very useful! Never used these. The alternative being the more verbose [1]. Thanks again, -j [1] #DATA :FRA a skos Concept; skos:notation “fre”^^euvoc:ISO_639_2B . #QUERY SELECT * WHERE { BIND ( "fre"^^xsd:string AS ?incoming )

[topbraid-users] custom datatypes and SPARQL

Hi, I had a long and complicated question, but in the process of writing it up I have found the answer completely on my own. Rather than throwing the text away, I thought why not share it. It is about the behaviour of complex datatypes in SPARQL. Sorry for the spam... For a project, we intend to

RE: [topbraid-users] question on restriction

he violations rather than a reasoner which creates an inconsistent (and hence useless for reasoning) ontology. Michael On Wed, Mar 25, 2020 at 7:01 AM Jan Voskuil mailto:jan.vosk...@taxonic.com>> wrote: Also, in OWL, constraints are constraints on classification, not constraints on specifyin

RE: [topbraid-users] question on restriction

Also, in OWL, constraints are constraints on classification, not constraints on specifying values of properties. It is often precisely the people who are slow in starting with SHACL that are not fully aware of this. Even with simple cardinality specified to exactly 1, a resource can have none o

RE: [topbraid-users] GeoSPARQL Support ?

Hi, We are helping customers use EDG in the domain of asset management, where GIS is always important. Our strategy so far has been: use a (top of the bill) GIS system (like ArcGIS Pro) for GIS, and cross-link between that and EDG. In that way, users are just a mouse click away from the asset det

RE: [topbraid-users] EDG

EDG is an enterprise platform, TBC is an IDE. I use TBC daily to create ontologies, convert TTL, run or test complex SPARQLs, and (I hope more and more) SPIN and SHACL Rule code. EDG is where graphs are shared for use by end users in custom applications. Data stewards use EDG for simple crud-tas

RE: [topbraid-users] Announcement: Release of TopBraid 6.3

Congratulations! 6.3 is really awesome. Keep up the good work, -j From: topbraid-users@googlegroups.com On Behalf Of TopQuadrant Sent: 11 December 2019 20:59 To: TopBraid Suite Users Subject: [topbraid-users] Announcement: Release of TopBraid 6.3 Dear Users, TopQuadrant is pleased to announce

RE: [topbraid-users] Generating a serialized graph with baseURI using CONSTRUCT

CONSTRUCT On 2 Dec 2019, at 12:34, Jan Voskuil mailto:jan.vosk...@taxonic.com>> wrote: Hi, The "# baseURI: " directive is typically generated by TBC. Often, one inserts the directive manually so that you can use or edit the serialized graph inside TBC. We generate seriali

[topbraid-users] Generating a serialized graph with baseURI using CONSTRUCT

Hi, The "# baseURI: " directive is typically generated by TBC. Often, one inserts the directive manually so that you can use or edit the serialized graph inside TBC. We generate serialized versions and copies of graphs using CONSTRUCT queries. But something like "# baseURI: http://example.org/my

Re: [topbraid-users] isDefinedBy usage

The spec is very clear: "This property may be used to indicate an RDF vocabulary in which a resource is described." If it is of any use: at KOOP, I use examples of rdfs:isDefinedBy to explain the notions of baseURI, owl:Ontology and namespace. URIs are "minted" in the graph where the correspondi

RE: [topbraid-users] Re: combining owl and skos

6.2.x for this edge case that’s fixed in 6.3 Beta. Cheers, David On 21 Nov 2019, at 11:33, Jan Voskuil mailto:jan.vosk...@taxonic.com>> wrote: Yes, when you are looking at the form for the BMW class (individual). But now make an instance of the BMW called “CarDavid” and look at the for

Re: [topbraid-users] Re: combining owl and skos

(Sorry, the prefix mapping pex needs to be fixed) Sent from my iPhone On 21 Nov 2019, at 12:33, Jan Voskuil wrote:  Yes, when you are looking at the form for the BMW class (individual). But now make an instance of the BMW called “CarDavid” and look at the form. The properties defined for

Re: [topbraid-users] Re: combining owl and skos

u > are not the addressee or if this message was sent to you by mistake, you > are requested to inform the sender and delete the message. TNO accepts no > liability for the content of this e-mail, for the manner in which you use > it and for damage of any kind resulting from the risks

Re: [topbraid-users] Re: combining owl and skos

The bottom line is that you should try this in TBC. Create the classes CarModel,BMW320i and TeslaModelS. Assert that the latter two instantiate the first. Create instances of the BMW and the Tesla. Define some properties for CarModel. TBC will not display the properties on the instance forms. T

Re: [topbraid-users] Re: combining owl and skos

by Holger to me earlier today: > dash:composite. I believe SHACL is seriously underused in tackling the > hairier problems in information modelling on the semantic web. > > On Tuesday, November 19, 2019 at 5:54:34 PM UTC+1, David Price wrote: >> >> >> >> O

[topbraid-users] Re: combining owl and skos

A very late after-burner (I am currently involved in similar discussions and stumbled upon this thread by accident): Have a look at Uschold's "Demystifying OWL". It is a good read, especially the two pages on punning. While there is little to add to what Irene and David have said, I think it is