Wot-thing-description: Evaluate geolocation terms in TD model (input from Profile TF)

Created on 5 Aug 2020 · 9Comments · Source: w3c/wot-thing-description

There are new vocabulary proposed in the latest Profile draft (also see https://github.com/w3c/wot-profile/issues/17). Which should evaluate how those should be covered in the core model. Which should also clarify which existing ontologies can be re-used for this kind of vocabulary.

See for a justification why loc_altitude is problematic.

new-term Geolocation

Source

sebastiankb

Most helpful comment

we should also check https://schema.org/GeoCoordinates

E.g.

{
  "@context": [
        "https://www.w3.org/2019/wot/td/v1",
        { "s": "http://schema.org" }
    ],
    "id": "urn:dev:ops:32473-WoTLamp-1234",
    "s:longitude": "40.75",
    "s:latitude": "73.98",
    "s:elevation": "15",
    "s:manufacturer": {"name": "Acme"},
    "title": "MyLampThing",
    ...
}

benfrancis on 12 Aug 2020

👍2

All 9 comments

for the geo based terms (loc_latitude, loc_longitude, loc_altitude, loc_height, loc_depth) we should check GeoSPARQL https://www.ogc.org/standards/geosparql which seems also to be used by SSN.

sebastiankb on 5 Aug 2020

👍2

here is another source https://www.w3.org/community/geosemweb/

sebastiankb on 5 Aug 2020

another (prominent) ontology https://lov.linkeddata.es/dataset/lov/vocabs/geo

sebastiankb on 6 Aug 2020

👍1

In today's TD call we discuss the option to define a geo container like geoLocation that embeds all geo-location based terms.

There is a discussion in the Use Case TF about different geo location standards: https://github.com/w3c/wot-thing-description/pull/927
A promising one seems to be https://www.w3.org/TR/geolocation-API , however, there is no RDF representation yet.
@mmccool will ask Dan Brickley if there are some plans
we should also check https://schema.org/GeoCoordinates and NGSI-LD

sebastiankb on 12 Aug 2020

we should also check https://schema.org/GeoCoordinates

E.g.

{
  "@context": [
        "https://www.w3.org/2019/wot/td/v1",
        { "s": "http://schema.org" }
    ],
    "id": "urn:dev:ops:32473-WoTLamp-1234",
    "s:longitude": "40.75",
    "s:latitude": "73.98",
    "s:elevation": "15",
    "s:manufacturer": {"name": "Acme"},
    "title": "MyLampThing",
    ...
}

benfrancis on 12 Aug 2020

👍2

I would also be for using the already existing vocabularies in schema.org

egekorkan on 12 Aug 2020

In Spatial Data on the Web Best Practices (2017), there is a Best Practice provided for "State how coordinate values are encoded" (Best Practice 8).

It uses both Basic Geo (WGS84 lat/long) Vocabulary and Schema.org.
It is also noted the definitions provided in schema.org do not indicate the unit of measure, as of 2017 at least.

takuki on 31 Aug 2020

From today's TD call:

for next draft it is recommended to provide examples how geo-based data can be integrated in TDs (e.g., based from schema.org)
there should be examples at top level and also within interaction level like in a property
it should be also explain that different ontologies can be used based on the use cases
@sebastiankb will provide a PR

sebastiankb on 9 Sep 2020

Don't think we should close this until we discuss with SDWIG and OCG, maybe write up an example (and include in the TD spec?). I've labelled this issue so it shows up in the joint meeting planned for Dec 10 (see https://github.com/w3c/wot/issues/939).