W3C home > Mailing lists > Public > public-sdwig@w3.org > June 2021

[sdw] Communicate good practice for defining geofences in the Best Practices doc (#1268)

From: Linda van den Brink via GitHub <sysbot+gh@w3.org>
Date: Wed, 16 Jun 2021 15:08:27 +0000
To: public-sdwig@w3.org
Message-ID: <issues.opened-922740718-1623856106-sysbot+gh@w3.org>
lvdbrink has just created a new issue for https://github.com/w3c/sdw:

== Communicate good practice for defining geofences in the Best Practices doc ==
Based on discussion we had on the [mailing list](https://lists.w3.org/Archives/Public/public-sdwig/2021Mar/0027.html) and in the SDWIG plenary session in May ([minutes](https://www.w3.org/2021/05/27-sdw-minutes.html)), we have come to the conclusion that 

1. We have the standards to define geofences
2. we lack a way to express the rules on behavior

Based on conclusion 1, we have said we want to add a best practice about geofencing to the [Best Practices document](https://www.w3.org/TR/sdw-bp/). 

@ogcscotts and @claraboyd volunteered to take this action.

Conclusion 2 indicates new work. As a first step, I propose we describe this lack we identified as a Gap in the [Gaps section of the Best Practices doc](https://www.w3.org/TR/sdw-bp/#conclusions). Next, we can search for people who are willing to take on a work item to fill this gap. 

### Background / summary of discussion so far
As @tguild told us, the Automotive group would like to come up with a modest set of parameters that could influence whether an application is permitted to sample data on a vehicle. One of the parameters is geofence boundaries, which is what they want the SDWIG's input on. Their geofence could be in the form of an amorphous shape on a map, boundary of municipalities, counties, regions or a radius.

OGC staff has done some work looking into geofences and has a lot of knowledge available ([see this report](https://www.ansi.org/standards-coordination/collaboratives-activities/unmanned-aircraft-systems-collaborative)). They found we have an appropriate suite of standards and knowledge for geofences. Geofences may be defined in increasingly complex ways, starting with a point and radius to a box to an arbitrary polygon to a buffer around a corridor. And those fences can be 2D or 3D in geometry and have temporal characteristics for a period of validity. Finally, geofences include or exclude, e.g., leaving a fenced area can result in a trigger or entering a fenced area can trigger an action.

There are privacy considerations to this. AR also has geofencing use cases.

Please view or discuss this issue at https://github.com/w3c/sdw/issues/1268 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 June 2021 15:08:56 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 16 June 2021 15:09:06 UTC