- From: John Goodwin <John.Goodwin@ordnancesurvey.co.uk>
- Date: Tue, 21 Jan 2014 19:33:48 +0000
- To: Raphaël Troncy <raphael.troncy@eurecom.fr>, "Andrea Perego" <andrea.perego@jrc.ec.europa.eu>, Frans Knibbe | Geodan <frans.knibbe@geodan.nl>
- CC: Sven Schade <sven.schade@jrc.ec.europa.eu>, "LocAdd W3C CG Public Mailing list" <public-locadd@w3.org>
Hi all, First - thank for the link Raphael - that did make me smile. The problems mixing work and social circles together ;) Anyway, here is my concrete example starter: If you look at the OS linked data for 'Southampton': http://data.ordnancesurvey.co.uk/id/7000000000037256 you will noticed that it is related to a 'Geometry' via the predicate 'extent' and it also has predicates geo:lat, geo:long and 'easting'/'northing'. geo:lat, geo:long and 'easting'/'northing' provide information about a 'representative point' for Southampton (centroid is a bit overloaded I think). This 'representative point' is just a point guaranteed to lie within Southampton. I think it is useful (in this case) to provide both the 'representative point' and the polygon for area Southampton covers. So something like: os:7000000000037256 a locn:Location; locn:representativePoint os:1234; locn:extent os:2458; os:1234 a sf:Point; os:2468 a sf:Polygon; ... or if you prefer: os:7000000000037256 a locn:Location; locn:representativePoint os:1234; locn:extent os:2458; os:1234 a neogeo:Point; os:2468 a neogeo:Polygon; ... Maybe then (in Manchester OWL syntax(ish)): locn:representativePoint rdfs:range (neogeo:Point OR sf:Point or geo:Point) locn:extent rdfs:range (neogeo:Polygon or sf:Polygon) (not saying representativePoint or extent are best choices for predicate names at this stage). John Dr John Goodwin Principal Scientist Research, Ordnance Survey Adanac Drive, SOUTHAMPTON, United Kingdom, SO16 0AS Phone: +44 (0) 23 8005 5761 www.ordnancesurvey.co.uk | john.goodwin@ordnancesurvey.co.uk Please consider your environmental responsibility before printing this email. -----Original Message----- From: Raphaël Troncy [mailto:raphael.troncy@eurecom.fr] Sent: 21 January 2014 15:40 To: Andrea Perego; Frans Knibbe | Geodan Cc: Sven Schade; LocAdd W3C CG Public Mailing list Subject: Re: Sub-properties for locn:geometry? Hello all, > In order to verify the current position of the group, could you please > five your vote to the following proposal: > > 1. Definition of sub-properties of locn:geometry to denote MBRs, > centroids, etc. > > 2. They can be used to specify the MBR, centroid, etc. of a dcterms:Location > > 3. They can be used to specify the MDR, centroid, etc. of a geometry Before we come to a vote (I'm not sure I understand fully those proposals by the way), can we have a *concrete* example (preferably in turtle) of how we express those things for each of the 3 variants? As an example, let's pick Southampton or a smaller district (*) of the city. Raphaël (*) For example, the district around https://www.foursquare.com/v/4bc1cd504cdfc9b60b0e9521 :-) Raphaël -- Raphaël Troncy EURECOM, Campus SophiaTech Multimedia Communications Department 450 route des Chappes, 06410 Biot, France. e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com Tel: +33 (0)4 - 9300 8242 Fax: +33 (0)4 - 9000 8200 Web: http://www.eurecom.fr/~troncy/ This email is only intended for the person to whom it is addressed and may contain confidential information. If you have received this email in error, please notify the sender and delete this email which must not be copied, distributed or disclosed to any other person. Unless stated otherwise, the contents of this email are personal to the writer and do not represent the official view of Ordnance Survey. Nor can any contract be formed on Ordnance Survey's behalf via email. We reserve the right to monitor emails and attachments without prior notice. Thank you for your cooperation. Ordnance Survey Adanac Drive Southampton SO16 0AS Tel: 08456 050505 http://www.ordnancesurvey.co.uk
Received on Tuesday, 21 January 2014 19:34:12 UTC