geosparql issue

33 views
Skip to first unread message

Bohms, H.M. (Michel)

unread,
Jul 26, 2022, 6:02:59 AM7/26/22
to topbrai...@googlegroups.com

Dear Holger,

When loading standard geosparql ontology (attached) in tbc I get:

 

 

Thx for advice, michel

 

 

 

Michel Böhms
Data Scientist

Unit Buildings, Infrastructure & Maritime


Mobile +31 630381220
E-mail  
michel...@tno.nl

Location

 

This message may contain information that is not intended for you. If you 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 inherent to the electronic transmission of messages.

 

 

 

geosparql.ttl

Holger Knublauch

unread,
Jul 26, 2022, 9:36:52 AM7/26/22
to topbrai...@googlegroups.com
The file seems to be invalid Turtle. Line 108. Other libraries also cannot parse that file.

Holger


On 26 Jul 2022, at 6:02 am, 'Bohms, H.M. (Michel)' via TopBraid Suite Users <topbrai...@googlegroups.com> wrote:

Dear Holger,
When loading standard geosparql ontology (attached) in tbc I get:
 
<image001.png>
 
Thx for advice, michel
 
 
 
Michel Böhms
Data Scientist
Unit Buildings, Infrastructure & Maritime
This message may contain information that is not intended for you. If you 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 inherent to the electronic transmission of messages.
 
<image003.png>
 
 

-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/8d4f2a38a51b4179ab9bc08171becfc7%40tno.nl.
<geosparql.ttl>

Bohms, H.M. (Michel)

unread,
Jul 27, 2022, 3:43:19 AM7/27/22
to topbrai...@googlegroups.com

Hi Holger,

 

So

 

              skos:example

                            spec11:B.1.2.4 ;

 

(and all other example clauses)

 

are invalid? (so the dots in the name?)

 

The strange thing is:

The turtle validator, http://ttl.summerofcode.be/ , says:

 

 

Isn’t it just a path with dots in it?

 

Thx michel

 

 

 

 

Michel Böhms
Data Scientist

Unit Buildings, Infrastructure & Maritime


Mobile +31 630381220
E-mail  
michel...@tno.nl

Location

 

This message may contain information that is not intended for you. If you 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 inherent to the electronic transmission of messages.

 

 

Bohms, H.M. (Michel)

unread,
Jul 27, 2022, 4:47:42 AM7/27/22
to topbrai...@googlegroups.com

Some more…

 

Suppose we have:

 

 

(having also a dot).

 

Wouldnt it be poss. to have an alternative shortend prefix like:

 

dc-short: http://purl.org/dc/

 

then resulting in dc:short:elements/1.1/

 

(similar like spec11:B.1.2.4 ;)

 

Gr michel

Marco Neumann

unread,
Jul 27, 2022, 5:24:22 AM7/27/22
to topbrai...@googlegroups.com
which should be 
and remove the last semicolon in line 108



--


---
Marco Neumann


Bohms, H.M. (Michel)

unread,
Jul 27, 2022, 5:34:07 AM7/27/22
to topbrai...@googlegroups.com

 

Even more:

 

The issue seems actually with red:

 

<http://www.opengis.net/ont/geosparql>

              a owl:Ontology ;

              dcterms:source "OGC GeoSPARQL – A Geographic Query Language for RDF Data OGC 11-052r5"@en ;

              rdfs:seeAlso <http://www.opengis.net/doc/IS/geosparql/1.1> ;

.

 

And now the weird thing:

 

Changing

 

              dcterms:source "OGC GeoSPARQL – A Geographic Query Language for RDF Data OGC 11-052r5"@en ;

to

              dcterms:source "x"@en ;

 

solves the issue…

 

????

 

Some strange control character somewhere?

Bohms, H.M. (Michel)

unread,
Jul 27, 2022, 5:37:35 AM7/27/22
to topbrai...@googlegroups.com

Yep sorry, was typo

 

Semicolon 108 seems fine to me.

 

I discovered in issue at some other plave in geosparql, see my next mail….

Bohms, H.M. (Michel)

unread,
Jul 27, 2022, 6:57:15 AM7/27/22
to topbrai...@googlegroups.com

Holger, I know you like minimal examples 😊

 

The dash is causing the issue …

 

              dcterms:source "GeoSPARQL "@en ;

 

deleting this dash solves the problem ….

 

Is this “a bit bigger than a normal dash” a special character not allowed in an rdf/turtle string?

David Price

unread,
Jul 27, 2022, 7:05:28 AM7/27/22
to topbrai...@googlegroups.com
I expect that is a special character that has to be escaped to be valid RDF Turtle.

See here and search for “escape” and you find:

Note

Prefixed names are a superset of XML QNames. They differ in that the local part of prefixed names may include:


Cheers,
David

On 27 Jul 2022, at 11:57, 'Bohms, H.M. (Michel)' via TopBraid Suite Users <topbrai...@googlegroups.com> wrote:

Holger, I know you like minimal examples 😊
 
The dash is causing the issue …
 
              dcterms:source "GeoSPARQL  "@en ;
 
deleting this dash solves the problem ….
 
Is this “a bit bigger than a normal dash” a special character not allowed in an rdf/turtle string?
 
 
 
Michel Böhms
Data Scientist
Unit Buildings, Infrastructure & Maritime
This message may contain information that is not intended for you. If you 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 inherent to the electronic transmission of messages.
 
<image002.png>
 
 
From: Bohms, H.M. (Michel) 
Sent: woensdag 27 juli 2022 11:38
To: 'topbrai...@googlegroups.com' <topbrai...@googlegroups.com>
Subject: RE: [topbraid-users] geosparql issue
 
Yep sorry, was typo
 
Semicolon 108 seems fine to me.
 
I discovered in issue at some other plave in geosparql, see my next mail….
 
 
 
Michel Böhms
Data Scientist
Unit Buildings, Infrastructure & Maritime
This message may contain information that is not intended for you. If you 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 inherent to the electronic transmission of messages.
 
<image002.png>
 
 
From: topbrai...@googlegroups.com <topbrai...@googlegroups.com> On Behalf Of Marco Neumann
Sent: woensdag 27 juli 2022 11:24
To: topbrai...@googlegroups.com
Subject: Re: [topbraid-users] geosparql issue
 
which should be 
 
 
and remove the last semicolon in line 108
 
On Wed, Jul 27, 2022 at 9:47 AM 'Bohms, H.M. (Michel)' via TopBraid Suite Users <topbrai...@googlegroups.com> wrote:
Some more…
 
Suppose we have:
 
 
(having also a dot).
 
Wouldnt it be poss. to have an alternative shortend prefix like:
 
 
then resulting in dc:short:elements/1.1/
 
(similar like spec11:B.1.2.4 ;)
 
Gr michel
 
 
 
 
 
Michel Böhms
Data Scientist
Unit Buildings, Infrastructure & Maritime
This message may contain information that is not intended for you. If you 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 inherent to the electronic transmission of messages.
 
<image002.png>
 
 
From: Bohms, H.M. (Michel) 
Sent: woensdag 27 juli 2022 09:43
To: topbrai...@googlegroups.com
Subject: RE: [topbraid-users] geosparql issue
 
Hi Holger,
 
So
 
              skos:example
                            spec11:B.1.2.4 ;
 
(and all other example clauses)
 
are invalid? (so the dots in the name?)
 
The strange thing is:
 
<image003.png>
 
Isn’t it just a path with dots in it?
 
Thx michel
 
 
 
 
Michel Böhms
Data Scientist
Unit Buildings, Infrastructure & Maritime
This message may contain information that is not intended for you. If you 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 inherent to the electronic transmission of messages.
 
<image002.png>
 

Bohms, H.M. (Michel)

unread,
Jul 27, 2022, 7:48:42 AM7/27/22
to topbrai...@googlegroups.com

Ok

But adding just a \ does not solve the issue

 

How would they need to escape in:

 

http://www.opengis.net/ont/geosparql

              a owl:Ontology ;

              dcterms:source http://www.opengis.net/doc/IS/geosparql/1.1 , "OGC GeoSPARQL – A Geographic Query Language for RDF Data OGC 11-052r5"@en ;

.

 

Then I can report that back to OGC (via our Dutch contact)

 

 

 

Michel Böhms
Data Scientist

Unit Buildings, Infrastructure & Maritime


Mobile +31 630381220
E-mail  
michel...@tno.nl

Location

 

This message may contain information that is not intended for you. If you 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 inherent to the electronic transmission of messages.

 

 

David Price

unread,
Jul 27, 2022, 8:16:45 AM7/27/22
to topbrai...@googlegroups.com
Hi Michel,

If you are talking to standards makers, then this detail is something to be understood with them using the RDF Turtle spec. It is not specific to TopBraid so you should do what the spec says, not what TQ says, and if that works in other tools but does not work correctly in TopBraid, then raise a ticket with Support. 

As you can see from what I pasted, I found something about QNames when you are actually looking at lang string-valued properties. I think the section you need may be this one 


with gory details about unicode (with links to the unicode standard) but I do not have time to test the various possibilities for you wrt the exact character being used (e.g. is that an emdash?) and its encoding:

Cheers,
David



On 27 Jul 2022, at 12:48, 'Bohms, H.M. (Michel)' via TopBraid Suite Users <topbrai...@googlegroups.com> wrote:

Ok
But adding just a \ does not solve the issue
 
How would they need to escape in:
 
              a owl:Ontology ;
              dcterms:source http://www.opengis.net/doc/IS/geosparql/1.1 , "OGC GeoSPARQL – A Geographic Query Language for RDF Data OGC 11-052r5"@en ;
.
 
Then I can report that back to OGC (via our Dutch contact)
 
 
 
Michel Böhms
Data Scientist
Unit Buildings, Infrastructure & Maritime

Bohms, H.M. (Michel)

unread,
Jul 27, 2022, 8:24:10 AM7/27/22
to topbrai...@googlegroups.com

All clear

 

I will advice them to use a normal dash to avoid gory unicode details 😊

 

 

 

Michel Böhms
Data Scientist

Unit Buildings, Infrastructure & Maritime


Mobile +31 630381220
E-mail  
michel...@tno.nl

Location

 

This message may contain information that is not intended for you. If you 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 inherent to the electronic transmission of messages.

 

 

Reply all
Reply to author
Forward
0 new messages