Name for new API for subscription events to location verification

[jlurien]

As agreed for #18, we should move the new API proposal in PR #49 to a new API spec. Which name do you prefer:

• geofencing
• location-verification-subscription
• Other, please suggest

[JoachimDahlgren]

The original description of the purpose of this new API that reads "So that developers are informed if a device is leaving or entering the "radius". This is important for tracking devices for Presetting of Homesettings or for tracking of logistics and more".

This aligns with how geofencing is usually described. Using the term geofencing would also be beneficial in case we later want to expand the API to handle multiple devices or even any device moving into or out of an area.

[alpaycetin74]

I tend to think geofencing is a better representation of what this api does.

[bigludo7]

Following @JoachimDahlgren explanation today in team meeting, I also think that geofencing is a better name (in particular to introduce later a geotracking api).

[jlurien]

For TEF, geofencing is also acceptable.

[akoshunyadi]

From DT side we can also accept geofencing. Althought we think that not use case specific names are generally better, but in this case the API is specific and the long name would just confuse API users.

[jlurien]

It seems that geofencing is the preferred name, so we can apply to #74 @akoshunyadi