Civic Relative Location draft-linsner-geopriv-relativeloc-02

1
Civic Relative Locationdraft-linsner-geopriv-rela
tiveloc-02

• Marc Linsner

2
draft-linsner-geopriv-relativeloc-02

• This document defines additional civic address
  parameters for use in Location Objects. The
  format is based on the civic address definition
  of PIDF-LO. These additional parameters allow
  expression of a relative location.

3
Use Case - Bob

• Bob is using an 802.11? device
• Bobs location
• 3675 Cisco Way
• San Jose, CA 95134
• US
• Building 13, 1st Floor

4
West
Bob
North
Bob is 30 feet west and 70 feet north of the
elevator
Reference Point
South
East
5
Use Case - Bob

• Bobs new location
• 3675 Cisco Way
• San Jose, CA 95134
• US
• Building 13, 1st Floor
• 30 feet west and 70 feet north of the elevator

6
Proposal

• Add additional CATypes to support relative
  location
• REFPT - Reference Point
• RELPOS-X - Relative Position X
• RELPOS-Y - Relative Position Y
• RELPOS-Z - Relative Position Z (optional)
• RELPOS-UOM - Units of measure (optional)
• (actual spelled wrong in the draft)

7
Other info

• This is additional data used to supplement Bobs
  civic location dataset
• The resultant location SHOULD not fall outside
  the bounds of the civic address boundary.

8
Why put this in the Civic doc?

• Its been suggested to create a compound
  location.
• The use case has been narrowed (I think) in the
  latest version such that this will only be used
  in a campus environment and civic location type.
• The users of this data believe this is a simply
  an extension of the civic data, the same as
  cubical number, seat number, etc.
• Its 3 additional tags.
• If a receiver doesnt understand the extra
  relative location tags, no information is lost,
  the same civic data we send today still applies.
• This does not prevent creating a compound
  location type for other relative location use
  cases.

9
Why N, S, E, W?

• Confusion on orientation
• Maybe building axes vs. geo axes?
• Yes, N, S, E, W can be confusing, but
  standardizing building shape/orientation is no
  less daunting.
• Providing right, left, straight directional's can
  lead to huge mistakes.

10
Next

• Fix the schema/namespace issue.
• Fix grammatical things.
• WG item?