Re: [Virtuoso-users] geometry data type in virtuoso

2016-11-10 Thread Kingsley Idehen 
On 11/9/16 10:25 PM, Peter F. Patel-Schneider wrote:
> Through a process of bisection I found the datum that is not handled by
> virtuoso.  It is
>
> wd:Q24227 a wikibase:Item ;
>   wdt:P625 " Point(351.83
> -14.47)"^^geo:wktLiteral .
>
> i.e., a point on Mars.
>
> Is virtuoso supposed to be able to handle other coordinate systems?  If not,
> how can it handle Wikidata and other information sources that have points not
> on the surface of the earth?
>
> peter

A valid RDF triple (or datum) would take the form:

wd:Q24227 a wikibase:Item ;
wdt:P625 "Point(351.83-14.47)"^^geo:wktLiteral .

Thus, you have a problematic triple. 


Kingsley


>
>
> On 11/08/2016 07:23 PM, Hugh Williams wrote:
>> Hi Peter,
>>
>> What is the Virtuoso version your are using ( run “virtuoso-t -?”) ?
>>
>> Against the latest 07.20.3217 build the following point geometry loads
>> successfully with the ttlp function:
>>
>> SQL> ttlp ('@prefix geo:  @prefix
>> virtrdf:   geo:geometry
>> "point(1.2 22.4"^^virtrdf:Geometry .', 'xxx', 'graph');
>>
>> Done. -- 10 msec.
>> SQL> sparql select * from  where {?s ?p ?o};
>> s
>> p
>> o
>> LONG VARCHAR 
>> LONG VARCHAR 
>> LONG VARCHAR
>> ___
>>
>> http://xxx/point 
>> http://www.w3.org/2003/01/geo/wgs84_pos#geometry 
>> POINT(1.200476837 22.3961853)
>>
>> 1 Rows. -- 2 msec.
>> SQL> 
>>
>> Best Regards
>> Hugh Williams
>> Professional Services
>> OpenLink Software, Inc.  //  http://www.openlinksw.com/
>> Weblog   -- http://www.openlinksw.com/blogs/
>> LinkedIn -- http://www.linkedin.com/company/openlink-software/
>> Twitter  -- http://twitter.com/OpenLink
>> Google+  -- http://plus.google.com/100570109519069333827/
>> Facebook -- http://www.facebook.com/OpenLinkSoftware
>> Universal Data Access, Integration, and Management Technology Providers
>>
>>> On 9 Nov 2016, at 02:34, Peter F. Patel-Schneider >> > wrote:
>>>
>>> Hi:
>>>
>>> I'm trying to get virtuoso to work with geometry data types.
>>>
>>> I noticed that the version of virtuoso that I am using requires that the 
>>> data
>>> type names be in ALL CAPS (e.g., POINT).   Has this been fixed in the 
>>> current
>>> version of virtuoso?
>>>
>>> peter
>>>
>>> --
>>> Developer Access Program for Intel Xeon Phi Processors
>>> Access to Intel Xeon Phi processor-based developer platforms.
>>> With one year of Intel Parallel Studio XE.
>>> Training and support from Colfax.
>>> Order your platform today. http://sdm.link/xeonphi
>>> ___
>>> Virtuoso-users mailing list
>>> Virtuoso-users@lists.sourceforge.net
>>> 
>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
> --
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> ___
> Virtuoso-users mailing list
> Virtuoso-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users


-- 
Regards,

Kingsley Idehen   
Founder & CEO 
OpenLink Software   (Home Page: http://www.openlinksw.com)

Weblogs (Blogs):
Legacy Blog: http://www.openlinksw.com/blog/~kidehen/
Blogspot Blog: http://kidehen.blogspot.com
Medium Blog: https://medium.com/@kidehen

Profile Pages:
Pinterest: https://www.pinterest.com/kidehen/
Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen
Twitter: https://twitter.com/kidehen
Google+: https://plus.google.com/+KingsleyIdehen/about
LinkedIn: http://www.linkedin.com/in/kidehen

Web Identities (WebID):
Personal: http://kingsley.idehen.net/dataspace/person/kidehen#this
: 
http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this




smime.p7s
Description: S/MIME Cryptographic Signature
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xe

Re: [Virtuoso-users] geometry data type in virtuoso

2016-11-10 Thread Jerven Tjalling Bolleman 
Dear Kingsley,

I imagine that Peter is referring to

Req 10
   All RDFS Literals of type geo:wktLiteral shall consist of an
optional URI identifying the coordinate reference system followed by
Simple Features Well Known Text (WKT) describing a geometric value.
Valid geo:wktLiterals are formed by concatenating a valid,
absolute URI as defined in [RFC 2396], one or more spaces (Unicode
U+0020 character) as a separator, and a WKT string as defined in
Simple Features [ISO 19125-1].

 From page vii of the GeoSPARQL standard. However, I can imagine that you 
have
few customers demanding GeoSPARQL support for Mars at this time ;)

So it is just a feature not yet implemented...

Regards,
Jerven

On 2016-11-10 14:06, Kingsley Idehen wrote:
> On 11/9/16 10:25 PM, Peter F. Patel-Schneider wrote:
>> Through a process of bisection I found the datum that is not handled 
>> by
>> virtuoso.  It is
>> 
>> wd:Q24227 a wikibase:Item ;
>>  wdt:P625 " Point(351.83
>> -14.47)"^^geo:wktLiteral .
>> 
>> i.e., a point on Mars.
>> 
>> Is virtuoso supposed to be able to handle other coordinate systems?  
>> If not,
>> how can it handle Wikidata and other information sources that have 
>> points not
>> on the surface of the earth?
>> 
>> peter
> 
> A valid RDF triple (or datum) would take the form:
> 
> wd:Q24227 a wikibase:Item ;
>   wdt:P625 "Point(351.83-14.47)"^^geo:wktLiteral .
> 
> Thus, you have a problematic triple.
> 
> 
> Kingsley
> 
> 
>> 
>> 
>> On 11/08/2016 07:23 PM, Hugh Williams wrote:
>>> Hi Peter,
>>> 
>>> What is the Virtuoso version your are using ( run “virtuoso-t -?”) ?
>>> 
>>> Against the latest 07.20.3217 build the following point geometry 
>>> loads
>>> successfully with the ttlp function:
>>> 
>>> SQL> ttlp ('@prefix geo:  
>>> @prefix
>>> virtrdf:   
>>> geo:geometry
>>> "point(1.2 22.4"^^virtrdf:Geometry .', 'xxx', 'graph');
>>> 
>>> Done. -- 10 msec.
>>> SQL> sparql select * from  where {?s ?p ?o};
>>> s
>>> p
>>> o
>>> LONG VARCHAR
>>> LONG VARCHAR
>>> LONG VARCHAR
>>> ___
>>> 
>>> http://xxx/point
>>> http://www.w3.org/2003/01/geo/wgs84_pos#geometry
>>> POINT(1.200476837 22.3961853)
>>> 
>>> 1 Rows. -- 2 msec.
>>> SQL>
>>> 
>>> Best Regards
>>> Hugh Williams
>>> Professional Services
>>> OpenLink Software, Inc.  //  
>>> http://www.openlinksw.com/
>>> Weblog   -- http://www.openlinksw.com/blogs/
>>> LinkedIn -- http://www.linkedin.com/company/openlink-software/
>>> Twitter  -- http://twitter.com/OpenLink
>>> Google+  -- http://plus.google.com/100570109519069333827/
>>> Facebook -- http://www.facebook.com/OpenLinkSoftware
>>> Universal Data Access, Integration, and Management Technology 
>>> Providers
>>> 
 On 9 Nov 2016, at 02:34, Peter F. Patel-Schneider 
 >>> > wrote:
 
 Hi:
 
 I'm trying to get virtuoso to work with geometry data types.
 
 I noticed that the version of virtuoso that I am using requires that 
 the data
 type names be in ALL CAPS (e.g., POINT).   Has this been fixed in 
 the current
 version of virtuoso?
 
 peter
 
 --
 Developer Access Program for Intel Xeon Phi Processors
 Access to Intel Xeon Phi processor-based developer platforms.
 With one year of Intel Parallel Studio XE.
 Training and support from Colfax.
 Order your platform today. http://sdm.link/xeonphi
 ___
 Virtuoso-users mailing list
 Virtuoso-users@lists.sourceforge.net
 
 https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>> --
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>> ___
>> Virtuoso-users mailing list
>> Virtuoso-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
> 
> 
> --
> Regards,
> 
> Kingsley Idehen   
> Founder & CEO
> OpenLink Software   (Home Page: http://www.openlinksw.com)
> 
> Weblogs (Blogs):
> Legacy Blog: http://www.openlinksw.com/blog/~kidehen/
> Blogspot Blog: http://kidehen.blogspot.com
> Medium Blog: https://medium.com/@kidehen
> 
> Profile Pages:
> Pinterest: https://www.pinterest.com/kidehen/
> Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen
> Twitter: https://twitter.com/kidehen
> Google+: https://plus.google.com/+KingsleyIdehen/about
> Linked

Re: [Virtuoso-users] geometry data type in virtuoso

2016-11-10 Thread Peter F. Patel-Schneider 
Is the problem that there is <> around the URI in
   Point(351.83 -14.47)
Otherwise this is in the lexical space for geo:wktLiteral.

Although the spec for geo:wktLiteral says that the lexical space consists of
an optional URI followed by a geometric value, the examples in the spec
enclose the URIs in <>.  I would expect that implementations of geo:wktLiteral
would thus allow enclosing <>.

Peter F. Patel-Schneider
Nuance Communications

On 11/10/2016 05:06 AM, Kingsley Idehen wrote:
> On 11/9/16 10:25 PM, Peter F. Patel-Schneider wrote:
>> Through a process of bisection I found the datum that is not handled by
>> virtuoso.  It is
>>
>> wd:Q24227 a wikibase:Item ;
>>  wdt:P625 " Point(351.83
>> -14.47)"^^geo:wktLiteral .
>>
>> i.e., a point on Mars.
>>
>> Is virtuoso supposed to be able to handle other coordinate systems?  If not,
>> how can it handle Wikidata and other information sources that have points not
>> on the surface of the earth?
>>
>> peter
> 
> A valid RDF triple (or datum) would take the form:
> 
> wd:Q24227 a wikibase:Item ;
>   wdt:P625 "Point(351.83-14.47)"^^geo:wktLiteral .
> 
> Thus, you have a problematic triple. 
> 
> 
> Kingsley
> 
> 
>>
>>
>> On 11/08/2016 07:23 PM, Hugh Williams wrote:
>>> Hi Peter,
>>>
>>> What is the Virtuoso version your are using ( run “virtuoso-t -?”) ?
>>>
>>> Against the latest 07.20.3217 build the following point geometry loads
>>> successfully with the ttlp function:
>>>
>>> SQL> ttlp ('@prefix geo:  @prefix
>>> virtrdf:   geo:geometry
>>> "point(1.2 22.4"^^virtrdf:Geometry .', 'xxx', 'graph');
>>>
>>> Done. -- 10 msec.
>>> SQL> sparql select * from  where {?s ?p ?o};
>>> s   
>>>  
>>> p   
>>>  
>>> o
>>> LONG VARCHAR
>>>  
>>> LONG VARCHAR
>>>  
>>> LONG VARCHAR
>>> ___
>>>
>>> http://xxx/point
>>>  
>>> http://www.w3.org/2003/01/geo/wgs84_pos#geometry
>>>  
>>> POINT(1.200476837 22.3961853)
>>>
>>> 1 Rows. -- 2 msec.
>>> SQL> 
>>>
>>> Best Regards
>>> Hugh Williams
>>> Professional Services
>>> OpenLink Software, Inc.  //  http://www.openlinksw.com/
>>> Weblog   -- http://www.openlinksw.com/blogs/
>>> LinkedIn -- http://www.linkedin.com/company/openlink-software/
>>> Twitter  -- http://twitter.com/OpenLink
>>> Google+  -- http://plus.google.com/100570109519069333827/
>>> Facebook -- http://www.facebook.com/OpenLinkSoftware
>>> Universal Data Access, Integration, and Management Technology Providers
>>>
 On 9 Nov 2016, at 02:34, Peter F. Patel-Schneider >>> > wrote:

 Hi:

 I'm trying to get virtuoso to work with geometry data types.

 I noticed that the version of virtuoso that I am using requires that the 
 data
 type names be in ALL CAPS (e.g., POINT).   Has this been fixed in the 
 current
 version of virtuoso?

 peter

 --
 Developer Access Program for Intel Xeon Phi Processors
 Access to Intel Xeon Phi processor-based developer platforms.
 With one year of Intel Parallel Studio XE.
 Training and support from Colfax.
 Order your platform today. http://sdm.link/xeonphi
 ___
 Virtuoso-users mailing list
 Virtuoso-users@lists.sourceforge.net
 
 https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>> --
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>> ___
>> Virtuoso-users mailing list
>> Virtuoso-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
> 
> 
> 
> 
> --
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> 
> 
> 
> ___
> V

Re: [Virtuoso-users] geometry data type in virtuoso

2016-11-10 Thread Kingsley Idehen 
On 11/10/16 8:29 AM, Jerven Tjalling Bolleman wrote:
> Dear Kingsley,
>
> I imagine that Peter is referring to
>
> Req 10
>   All RDFS Literals of type geo:wktLiteral shall consist of an
> optional URI identifying the coordinate reference system followed by
> Simple Features Well Known Text (WKT) describing a geometric value.
> Valid geo:wktLiterals are formed by concatenating a valid,
> absolute URI as defined in [RFC 2396], one or more spaces (Unicode
> U+0020 character) as a separator, and a WKT string as defined in
> Simple Features [ISO 19125-1].
>
> From page vii of the GeoSPARQL standard. However, I can imagine that
> you have
> few customers demanding GeoSPARQL support for Mars at this time ;)
>
> So it is just a feature not yet implemented...
>
> Regards,
> Jerven

Hi Jerven,

Correct.

We are considering adding this syntax sugar atop our GeoData processing
capability, but at the current time we don't have an ETA.


Kingsley
>
> On 2016-11-10 14:06, Kingsley Idehen wrote:
>> On 11/9/16 10:25 PM, Peter F. Patel-Schneider wrote:
>>> Through a process of bisection I found the datum that is not handled by
>>> virtuoso.  It is
>>>
>>> wd:Q24227 a wikibase:Item ;
>>> wdt:P625 " Point(351.83
>>> -14.47)"^^geo:wktLiteral .
>>>
>>> i.e., a point on Mars.
>>>
>>> Is virtuoso supposed to be able to handle other coordinate systems? 
>>> If not,
>>> how can it handle Wikidata and other information sources that have
>>> points not
>>> on the surface of the earth?
>>>
>>> peter
>>
>> A valid RDF triple (or datum) would take the form:
>>
>> wd:Q24227 a wikibase:Item ;
>> wdt:P625 "Point(351.83-14.47)"^^geo:wktLiteral .
>>
>> Thus, you have a problematic triple.
>>
>>
>> Kingsley
>>
>>
>>>
>>>
>>> On 11/08/2016 07:23 PM, Hugh Williams wrote:
 Hi Peter,

 What is the Virtuoso version your are using ( run “virtuoso-t -?”) ?

 Against the latest 07.20.3217 build the following point geometry loads
 successfully with the ttlp function:

 SQL> ttlp ('@prefix geo: 
 @prefix
 virtrdf:  
 geo:geometry
 "point(1.2 22.4"^^virtrdf:Geometry .', 'xxx', 'graph');

 Done. -- 10 msec.
 SQL> sparql select * from  where {?s ?p ?o};
 s
 p
 o
 LONG VARCHAR
 LONG VARCHAR
 LONG VARCHAR
 ___


 http://xxx/point
 http://www.w3.org/2003/01/geo/wgs84_pos#geometry
 POINT(1.200476837 22.3961853)

 1 Rows. -- 2 msec.
 SQL>

 Best Regards
 Hugh Williams
 Professional Services
 OpenLink Software, Inc.  // 
 http://www.openlinksw.com/
 Weblog   -- http://www.openlinksw.com/blogs/
 LinkedIn -- http://www.linkedin.com/company/openlink-software/
 Twitter  -- http://twitter.com/OpenLink
 Google+  -- http://plus.google.com/100570109519069333827/
 Facebook -- http://www.facebook.com/OpenLinkSoftware
 Universal Data Access, Integration, and Management Technology
 Providers

> On 9 Nov 2016, at 02:34, Peter F. Patel-Schneider
>  > wrote:
>
> Hi:
>
> I'm trying to get virtuoso to work with geometry data types.
>
> I noticed that the version of virtuoso that I am using requires
> that the data
> type names be in ALL CAPS (e.g., POINT).   Has this been fixed in
> the current
> version of virtuoso?
>
> peter
>
> --
>
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> ___
> Virtuoso-users mailing list
> Virtuoso-users@lists.sourceforge.net
> 
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>> --
>>>
>>> Developer Access Program for Intel Xeon Phi Processors
>>> Access to Intel Xeon Phi processor-based developer platforms.
>>> With one year of Intel Parallel Studio XE.
>>> Training and support from Colfax.
>>> Order your platform today. http://sdm.link/xeonphi
>>> ___
>>> Virtuoso-users mailing list
>>> Virtuoso-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>
>>
>> -- 
>> Regards,
>>
>> Kingsley Idehen   
>> Founder & CEO
>> OpenLink Software   (Home Page: http://www.openlinksw.com)
>>
>> Weblogs (Blogs):
>> Legacy Blog: http://www.openlinksw.

Re: [Virtuoso-users] geometry data type in virtuoso

2016-11-10 Thread Kingsley Idehen 
On 11/10/16 12:13 PM, Peter F. Patel-Schneider wrote:
> Is the problem that there is <> around the URI in
>    Point(351.83 -14.47)
> Otherwise this is in the lexical space for geo:wktLiteral.
>
> Although the spec for geo:wktLiteral says that the lexical space consists of
> an optional URI followed by a geometric value, the examples in the spec
> enclose the URIs in <>.  I would expect that implementations of geo:wktLiteral
> would thus allow enclosing <>.
>
> Peter F. Patel-Schneider
> Nuance Communications

Hi Peter,

We don't support this GeoSPARQL notation for datum representation at
this time. We do plan to get this added in the not too distant future. I
just can't give a specific ETA at this point in time.

Kingsley 
>
> On 11/10/2016 05:06 AM, Kingsley Idehen wrote:
>> On 11/9/16 10:25 PM, Peter F. Patel-Schneider wrote:
>>> Through a process of bisection I found the datum that is not handled by
>>> virtuoso.  It is
>>>
>>> wd:Q24227 a wikibase:Item ;
>>> wdt:P625 " Point(351.83
>>> -14.47)"^^geo:wktLiteral .
>>>
>>> i.e., a point on Mars.
>>>
>>> Is virtuoso supposed to be able to handle other coordinate systems?  If not,
>>> how can it handle Wikidata and other information sources that have points 
>>> not
>>> on the surface of the earth?
>>>
>>> peter
>> A valid RDF triple (or datum) would take the form:
>>
>> wd:Q24227 a wikibase:Item ;
>>  wdt:P625 "Point(351.83-14.47)"^^geo:wktLiteral .
>>
>> Thus, you have a problematic triple. 
>>
>>
>> Kingsley
>>
>>
>>>
>>> On 11/08/2016 07:23 PM, Hugh Williams wrote:
 Hi Peter,

 What is the Virtuoso version your are using ( run “virtuoso-t -?”) ?

 Against the latest 07.20.3217 build the following point geometry loads
 successfully with the ttlp function:

 SQL> ttlp ('@prefix geo:  @prefix
 virtrdf:   geo:geometry
 "point(1.2 22.4"^^virtrdf:Geometry .', 'xxx', 'graph');

 Done. -- 10 msec.
 SQL> sparql select * from  where {?s ?p ?o};
 s  
   
 p  
   
 o
 LONG VARCHAR   
   
 LONG VARCHAR   
   
 LONG VARCHAR
 ___

 http://xxx/point   
   
 http://www.w3.org/2003/01/geo/wgs84_pos#geometry   
   
 POINT(1.200476837 22.3961853)

 1 Rows. -- 2 msec.
 SQL> 

 Best Regards
 Hugh Williams
 Professional Services
 OpenLink Software, Inc.  //  http://www.openlinksw.com/
 Weblog   -- http://www.openlinksw.com/blogs/
 LinkedIn -- http://www.linkedin.com/company/openlink-software/
 Twitter  -- http://twitter.com/OpenLink
 Google+  -- http://plus.google.com/100570109519069333827/
 Facebook -- http://www.facebook.com/OpenLinkSoftware
 Universal Data Access, Integration, and Management Technology Providers

> On 9 Nov 2016, at 02:34, Peter F. Patel-Schneider  > wrote:
>
> Hi:
>
> I'm trying to get virtuoso to work with geometry data types.
>
> I noticed that the version of virtuoso that I am using requires that the 
> data
> type names be in ALL CAPS (e.g., POINT).   Has this been fixed in the 
> current
> version of virtuoso?
>
> peter
>
> --
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> ___
> Virtuoso-users mailing list
> Virtuoso-users@lists.sourceforge.net
> 
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>> --
>>> Developer Access Program for Intel Xeon Phi Processors
>>> Access to Intel Xeon Phi processor-based developer platforms.
>>> With one year of Intel Parallel Studio XE.
>>> Training and support from Colfax.
>>> Order your platform today. http://sdm.link/xeonphi
>>> ___
>>> Virtuoso-users mailing list
>>> Virtuoso-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>
>>
>>
>> --

Re: [Virtuoso-users] geometry data type in virtuoso

2016-11-10 Thread Peter F. Patel-Schneider 
So when you implied that
wd:Q24227 a wikibase:Item ;
 wdt:P625 " Point(351.83
-14.47)"^^geo:wktLiteral .
had an invalid triple you didn't really mean that.

peter



On 11/10/2016 10:24 AM, Kingsley Idehen wrote:
> On 11/10/16 12:13 PM, Peter F. Patel-Schneider wrote:
>> Is the problem that there is <> around the URI in
>>    Point(351.83 -14.47)
>> Otherwise this is in the lexical space for geo:wktLiteral.
>>
>> Although the spec for geo:wktLiteral says that the lexical space consists of
>> an optional URI followed by a geometric value, the examples in the spec
>> enclose the URIs in <>.  I would expect that implementations of 
>> geo:wktLiteral
>> would thus allow enclosing <>.
>>
>> Peter F. Patel-Schneider
>> Nuance Communications
> 
> Hi Peter,
> 
> We don't support this GeoSPARQL notation for datum representation at
> this time. We do plan to get this added in the not too distant future. I
> just can't give a specific ETA at this point in time.
> 
> Kingsley 
>>
>> On 11/10/2016 05:06 AM, Kingsley Idehen wrote:
>>> On 11/9/16 10:25 PM, Peter F. Patel-Schneider wrote:
 Through a process of bisection I found the datum that is not handled by
 virtuoso.  It is

 wd:Q24227 a wikibase:Item ;
wdt:P625 " Point(351.83
 -14.47)"^^geo:wktLiteral .

 i.e., a point on Mars.

 Is virtuoso supposed to be able to handle other coordinate systems?  If 
 not,
 how can it handle Wikidata and other information sources that have points 
 not
 on the surface of the earth?

 peter
>>> A valid RDF triple (or datum) would take the form:
>>>
>>> wd:Q24227 a wikibase:Item ;
>>> wdt:P625 "Point(351.83-14.47)"^^geo:wktLiteral .
>>>
>>> Thus, you have a problematic triple. 
>>>
>>>
>>> Kingsley
>>>
>>>

 On 11/08/2016 07:23 PM, Hugh Williams wrote:
> Hi Peter,
>
> What is the Virtuoso version your are using ( run “virtuoso-t -?”) ?
>
> Against the latest 07.20.3217 build the following point geometry loads
> successfully with the ttlp function:
>
> SQL> ttlp ('@prefix geo:  
> @prefix
> virtrdf:   geo:geometry
> "point(1.2 22.4"^^virtrdf:Geometry .', 'xxx', 'graph');
>
> Done. -- 10 msec.
> SQL> sparql select * from  where {?s ?p ?o};
> s 
>
> p 
>
> o
> LONG VARCHAR  
>
> LONG VARCHAR  
>
> LONG VARCHAR
> ___
>
> http://xxx/point  
>
> http://www.w3.org/2003/01/geo/wgs84_pos#geometry  
>
> POINT(1.200476837 22.3961853)
>
> 1 Rows. -- 2 msec.
> SQL> 
>
> Best Regards
> Hugh Williams
> Professional Services
> OpenLink Software, Inc.  //  http://www.openlinksw.com/
> Weblog   -- http://www.openlinksw.com/blogs/
> LinkedIn -- http://www.linkedin.com/company/openlink-software/
> Twitter  -- http://twitter.com/OpenLink
> Google+  -- http://plus.google.com/100570109519069333827/
> Facebook -- http://www.facebook.com/OpenLinkSoftware
> Universal Data Access, Integration, and Management Technology Providers
>
>> On 9 Nov 2016, at 02:34, Peter F. Patel-Schneider > > wrote:
>>
>> Hi:
>>
>> I'm trying to get virtuoso to work with geometry data types.
>>
>> I noticed that the version of virtuoso that I am using requires that the 
>> data
>> type names be in ALL CAPS (e.g., POINT).   Has this been fixed in the 
>> current
>> version of virtuoso?
>>
>> peter
>>
>> --
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>> ___
>> Virtuoso-users mailing list
>> Virtuoso-users@lists.sourceforge.net
>> 
>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
 --
 Developer Access Program for Intel Xeon Phi Processors
 Access

Re: [Virtuoso-users] geometry data type in virtuoso

2016-11-10 Thread Peter F. Patel-Schneider 
I modified rdfbox.c to take out the two (!) checks that object to literals of
type geo:wktLiteral with coordinate system URIs.  Currently I'm loading a
wikidata dump into virtuoso and nothing is complaining (so far).

I expect that working with this data will produce query-time errors when
trying to do geographic operations on these values.  Hopefully these errors
will produce SPARQL errors that can be handled and not bring down virtuoso.

peter

PS:  I would be nice to be able to turn the errors into warnings, but I
couldn't figure out how to do that.

PPS:  It also would be nice to have an option that ignores triples with
problems when loading large RDF documents.  I think that this has been asked
for in the past as well.


On 11/10/2016 05:29 AM, Jerven Tjalling Bolleman wrote:
> Dear Kingsley,
> 
> I imagine that Peter is referring to
> 
> Req 10
>All RDFS Literals of type geo:wktLiteral shall consist of an
> optional URI identifying the coordinate reference system followed by
> Simple Features Well Known Text (WKT) describing a geometric value.
> Valid geo:wktLiterals are formed by concatenating a valid,
> absolute URI as defined in [RFC 2396], one or more spaces (Unicode
> U+0020 character) as a separator, and a WKT string as defined in
> Simple Features [ISO 19125-1].
> 
>  From page vii of the GeoSPARQL standard. However, I can imagine that you 
> have
> few customers demanding GeoSPARQL support for Mars at this time ;)
> 
> So it is just a feature not yet implemented...
> 
> Regards,
> Jerven
> 
> On 2016-11-10 14:06, Kingsley Idehen wrote:
>> On 11/9/16 10:25 PM, Peter F. Patel-Schneider wrote:
>>> Through a process of bisection I found the datum that is not handled 
>>> by
>>> virtuoso.  It is
>>>
>>> wd:Q24227 a wikibase:Item ;
>>> wdt:P625 " Point(351.83
>>> -14.47)"^^geo:wktLiteral .
>>>
>>> i.e., a point on Mars.
>>>
>>> Is virtuoso supposed to be able to handle other coordinate systems?  
>>> If not,
>>> how can it handle Wikidata and other information sources that have 
>>> points not
>>> on the surface of the earth?
>>>
>>> peter
>>
>> A valid RDF triple (or datum) would take the form:
>>
>> wd:Q24227 a wikibase:Item ;
>>  wdt:P625 "Point(351.83-14.47)"^^geo:wktLiteral .
>>
>> Thus, you have a problematic triple.
>>
>>
>> Kingsley
>>
>>
>>>
>>>
>>> On 11/08/2016 07:23 PM, Hugh Williams wrote:
 Hi Peter,

 What is the Virtuoso version your are using ( run “virtuoso-t -?”) ?

 Against the latest 07.20.3217 build the following point geometry 
 loads
 successfully with the ttlp function:

 SQL> ttlp ('@prefix geo:  
 @prefix
 virtrdf:   
 geo:geometry
 "point(1.2 22.4"^^virtrdf:Geometry .', 'xxx', 'graph');

 Done. -- 10 msec.
 SQL> sparql select * from  where {?s ?p ?o};
 s
 p
 o
 LONG VARCHAR
 LONG VARCHAR
 LONG VARCHAR
 ___

 http://xxx/point
 http://www.w3.org/2003/01/geo/wgs84_pos#geometry
 POINT(1.200476837 22.3961853)

 1 Rows. -- 2 msec.
 SQL>

 Best Regards
 Hugh Williams
 Professional Services
 OpenLink Software, Inc.  //  
 http://www.openlinksw.com/
 Weblog   -- http://www.openlinksw.com/blogs/
 LinkedIn -- http://www.linkedin.com/company/openlink-software/
 Twitter  -- http://twitter.com/OpenLink
 Google+  -- http://plus.google.com/100570109519069333827/
 Facebook -- http://www.facebook.com/OpenLinkSoftware
 Universal Data Access, Integration, and Management Technology 
 Providers

> On 9 Nov 2016, at 02:34, Peter F. Patel-Schneider 
>  > wrote:
>
> Hi:
>
> I'm trying to get virtuoso to work with geometry data types.
>
> I noticed that the version of virtuoso that I am using requires that 
> the data
> type names be in ALL CAPS (e.g., POINT).   Has this been fixed in 
> the current
> version of virtuoso?
>
> peter
>
> --
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> ___
> Virtuoso-users mailing list
> Virtuoso-users@lists.sourceforge.net
> 
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>> --
>>> Developer Access Program for Intel Xeon Phi Proces

Re: [Virtuoso-users] Adding a public SPARQL endpoint

2016-11-10 Thread Arun Balagopalan 
Hi Hugh,

Changing the vhost to the ec2 hostname (ec2...amazonaws.com) did the trick.
I was thinking it needed to be localhost because it was running inside
docker.

Many thanks,
Arun


On Tue, Nov 8, 2016 at 4:12 PM, Hugh Williams 
wrote:

> Hi Arun,
>
> Where are you accessing the docket AMI from via HTTP , I assume a machine
> remote to it ?
>
> In which case the “vhost” value should be the actual hostname or cname of
> the docker you want the /sparql endpoint to be accessible on, as
> “localhost” is not accessible from a remote machine for which localhost
> would be itself.
>
>
> Best Regards
> Hugh Williams
> Professional Services
> OpenLink Software, Inc.  //  http://www.openlinksw.com/
> Weblog   -- http://www.openlinksw.com/blogs/
> LinkedIn -- http://www.linkedin.com/company/openlink-software/
> Twitter  -- http://twitter.com/OpenLink
> Google+  -- http://plus.google.com/100570109519069333827/
> Facebook -- http://www.facebook.com/OpenLinkSoftware
> Universal Data Access, Integration, and Management Technology Providers
>
> On 8 Nov 2016, at 21:47, Arun Balagopalan  wrote:
>
> Hi Christos,
>
> Thanks for the answer. I was trying to do what you suggested initially,
> but could not figure out how to set the HTTP host to  {Default Web Site}.
> Since I was getting to the index page with localhost, I thought the
> necessary listeners were added.
>
> When I click export for the SPARQL endpoints, this is what I get. Not sure
> if that's useful, but you see *ini* for the default endpoint, which could
> indicate values coming from virtuoso.ini or some default set.
>
> For Default endpoint
>
> DB.DBA.VHOST_REMOVE (
>lhost=>'*ini*',
>vhost=>'*ini*',
>lpath=>'/sparql'
> );
>
> DB.DBA.VHOST_DEFINE (
>lhost=>'*ini*',
>vhost=>'*ini*',
>lpath=>'/sparql',
>ppath=>'/!sparql/',
>is_dav=>1,
>is_brws=>0,
>vsp_user=>'dba',
>ses_vars=>0,
>opts=>vector ('noinherit', 1),
>is_default_host=>0
> );
>
> New endpoint
>
> DB.DBA.VHOST_REMOVE (
>lhost=>':80',
>vhost=>'localhost',
>lpath=>'/sparql'
> );
>
> DB.DBA.VHOST_DEFINE (
>lhost=>':80',
>vhost=>'localhost',
>lpath=>'/sparql',
>ppath=>'/!sparql/',
>is_dav=>1,
>is_brws=>0,
>def_page=>'',
>vsp_user=>'dba',
>ses_vars=>0,
>opts=>vector ('browse_sheet', '', 'noinherit', 'yes'),
>is_default_host=>0
> );
>
>
> Cheers,
> Arun
>
> On Tue, Nov 8, 2016 at 1:57 AM, Christos Skodras <
> christos.skod...@europeana.eu> wrote:
>
>> Hello Arun,
>>
>>
>>
>> I think your problem is that only localhost listens on port 80. Can you
>> configure your http-host with the {Default Web Site} instead of localhost?
>>
>>
>> *Christos Skodras*
>> Senior System Developer
>>
>>
>> T: +31 (0)70 314 0680
>> M:
>> E: christos.skod...@europeana.eu
>> Skype:
>>
>>
>>
>> *Be part of Europe's online cultural movement - join the Europeana
>> Network Association: http://bit.ly/NetworkAssociation
>> *
>>
>>  *#AllezCulture!*
>> Disclaimer: This email and any files transmitted with it are confidential
>> and intended solely for the use of the individual or entity to whom they
>> are addressed. If you have received this email in error please notify the
>> system manager. If you are not the named addressee you should not
>> disseminate, distribute or copy this email. Please notify the sender
>> immediately by email if you have received this email by mistake and delete
>> this email from your system.
>>
>> *From: *Arun Balagopalan 
>> *Date: *Tuesday, 8 November 2016 at 10:32
>> *To: *"virtuoso-users@lists.sourceforge.net" <
>> virtuoso-users@lists.sourceforge.net>
>> *Subject: *[Virtuoso-users] Adding a public SPARQL endpoint
>>
>>
>>
>> Hi all,
>>
>>
>>
>> I am trying to add a public, protected sparql endpoint to my Virtuoso
>> server. In my case, Virtuoso is running in a Docker container on an ec2
>> machine. The end goal is to have a SPARQL server listening on port 80 on
>> the ec2 host (by binding to port 80 in docker).
>>
>>
>>
>> As per the solution here
>> 
>>  and
>> similar references in the wiki, I added a new sparql endpoint with port 80
>> and localhost (since it is running inside docker). I am able to get to a
>> default page using the ec2 machine's public ip address [1] , but accessing
>> /sparql gives me a 404.
>>
>>
>>
>> My settings for the new endpoint can be seen in [2] [3]. Also, I'm not
>> adding authentication for now, figured it would be easy to protect it later.
>>
>>
>>
>> Since this seems like a common use case, hoping somebody will point me in
>> the right direction :)
>>
>>
>>
>> [1] http://imgur.com/1DyyWwg
>>
>> [2] http://imgur.com/hRPYgP1
>>
>> [3] http://imgur.com/ChUMz6f
>>
>>
>>
>>
>>
>> Thanks,
>>
>> Arun
>>
>
> ---