- From: Martin Hepp <martin.hepp@ebusiness-unibw.org>
- Date: Thu, 18 Jul 2013 11:48:37 +0200
- To: Dan Brickley <danbri@danbri.org>
- Cc: "public-vocabs@w3.org Org" <public-vocabs@w3.org>
Dear Dan, all: If I am not mentally retarded, I am pretty sure that until yesterday, the geo property could also have been attached to a http://schema.org/PostalAddress. Now it seems to be gone and the Google Structured Data Testing tool starts complaining that geo was not defined for PostalAddress in schema.org. It is still available for http://schema.org/Place and its subtypes, as expected. Is that correct? I think that from a conceptual modeling perspective, both is arguably correct. Attaching the geo-position to a place and to an address means using the same property with two slightly different meaning: - geo attached to a place means the place can be found at that position - geo attached to an address means the address approximately translates to the geo-position. So it is "ontologically" cleaner as it is now. From a search engine perspective, however, you may want to allow people to support the translation from addresses to geo-positions or to provide precise geo-position if the address encompasses a bigger polygon. Martin -------------------------------------------------------- martin hepp e-business & web science research group universitaet der bundeswehr muenchen e-mail: hepp@ebusiness-unibw.org phone: +49-(0)89-6004-4217 fax: +49-(0)89-6004-4620 www: http://www.unibw.de/ebusiness/ (group) http://www.heppnetz.de/ (personal) skype: mfhepp twitter: mfhepp Check out GoodRelations for E-Commerce on the Web of Linked Data! ================================================================= * Project Main Page: http://purl.org/goodrelations/
Received on Thursday, 18 July 2013 09:49:05 UTC