search

camaraproject / DeviceLocation

Repository to describe, develop, document and test the DeviceLocation API family
Apache License 2.0
21 stars 32 forks source link

Differentiate basePaths for APIS for location verification vs location retrieval #59

Closed jlurien closed 1 year ago

jlurien commented 1 year ago

Our current spec uses basePath = location, but we are now proposing a new API within this WG, and as they are separate APIs they must have different basePath.

Proposal is to rename current one to location-verification and the new one could keep just location, or even location-retrieval, to make it more explicit.

Thoughts, preferences?

sfnuser commented 1 year ago

I agree with location-verification rename and the new one shall be location as it is a GET.

I also wonder why basePath needs to be a variable in the spec. Can it not be hardcoded?

jlurien commented 1 year ago

I agree with location-verification rename and the new one shall be location as it is a GET.

I also wonder why basePath needs to be a variable in the spec. Can it not be hardcoded?

It could be hardcoded, no practical difference

nickvenezia commented 1 year ago

When location is recorded, should it be recorded who requested the info?

jlurien commented 1 year ago

When location is recorded, should it be recorded who requested the info?

How is that question related to this issue? Feel free to open new issues to raise anything new so people can focus on the topic.

jlurien commented 1 year ago

To be updated as device-location-verification