[Concept]: AtX subjective Location concepts

[coolharsh55]

Specs

Locations (LOC)

New Concept(s)

Add AtX concepts to the LOC extension for subjective locations, such as AtWork, AtOffice, AtHome, AtPublicPark, and so on to express locations that don't have a legally defined identity (as compared to a Country) but are useful to accurately state the location as described within the use-case.

Some subjective concepts already exist within DPV as LocationLocality e.g. WithinDevice and PublicLocation - these should remain in DPV (to avoid breaking changes) but should be extended in the LOC extension.

Changed Concept(s)

No response

[coolharsh55]

We discussed this in Meeting FEB-06 and agreed to include it in scope. For how to model such concepts, I have noted my thoughts here: https://harshp.com/dev/dpv/locations-01. The gist is as follows:

• LocationsByConfidentiality
  • PersonalPlace - the space around or defined by an individual which defines their comfort, autonomy, privacy, and other attributes which relate to their 'person'.
  • PrivatePlace - a place that is controlled privately, or that is not a public space.
  • PublicPlace - a place which members of the public can access or are permitted to access, whether by right or by express or implied permission, or whether on payment or otherwise.
  • PubliclyAccessiblePrivatePlace - defined by extending both private and public place concepts
• LocationsByExistence
  • PhysicalLocation further expanded with concepts such as home, office, etc.
  • VirtualLocation further expanded with concepts such as device, app, etc.

In the above, whether to prefix concepts for home, device, etc. as AtHome, InHome, WithinHome, HomeLocation should be discussed so as to prevent misuse e.g. Home as location may get confused with home as personal data, whereas the prefixed forms are less likely to be mistaken.

Edit: If some process uses home as location, then home is indeed personal data. Should we then model this as a subjective location AND as personal data?

[coolharsh55]

(using dpvbot:) This was discussed in Meeting 2025-02-13
The basic top concepts should be tested in various combinations to ensure its a good model, and then we expand the taxonomy with more specific concepts.

[bact]

  * `PubliclyAccessiblePrivatePlace` - defined by extending both private and public place concepts

A popular term (from urban planning) similar to this is "privately owned public space" (POPS). But as the term involves ownership, it may complicated the concepts under "-ByConfidentiality".

[coolharsh55]

Thanks @bact - that's exactly the concept we want. I looked through it and others and have captured my thoughts here: https://harshp.com/dev/dpv/locations-03. Summary below.

1. PrivateSpace - a space that is owned or controlled by a private entity and where access to members of the public is restricted.
   a. PersonalSpace - a private space associated with an individual in a personal capacity - such as their home or the space around their physical person e.g. my home or my room.
   b. PrivatelyOwnedPlace - a place that is privately owned e.g. offices, malls.
   c. SemiPrivateSpace - a private space that acts as a shared space with other entities but which is still essentially private e.g. a semi-private hospital room shared with another patient.
   d. PrivateCommunalSpace - a space that is accessible to a group or a community within a private space and where members of the public do not have access to it e.g. society amenities such as gyms and pools.
2. PublicSpace - any space that is accessible to the public or is owned by the public (note: this is distinct from government ownership which can exclude public access from the place).
   a. PubliclyAccessibleSpace - a space that is accessible to all members of the public e.g. parks, malls, train stations. (note: this concept should be expanded in EU-AIAct extension with the Recital 19 definition.)
   b. PubliclyOwnedSpace - a space that is owned by the public e.g. national parks, forests.
3. SemiPublicSpace - a space that is a hybrid space i.e it has both public and private components - such as by having part of it be a private space or which is operated privately.
   a. PrivatelyOwnedPublicPlace - a space that is privately owned but which is accessible and usable by the public - whether freely or through a process which is open to all members of the public e.g. hotel lobby, shopping mall atriums. (note: this extends PubliclyAccessibleSpace and PrivatelyOwnedPlace.)
   b. PrivatelyOperatedPublicPlace - a space that is operated or managed by a private entity but which is accessible to the public e.g. a public bus station operated by a specific company. (note: this extends PubliclyAccessibleSpace and not PublicSpace.)

In addition to the above, the working note also talks about modelling VirtualLocation. For cookies, it suggests PrivateVirtualLocation and then to extend it as ExternallyManagedVirtualLocation which enables distinguishing when someone else is controlling a 'private space'.

[coolharsh55]

Based on last meeting FEB-20 I collected below use-cases and created examples in a blog post. The only concepts not present are those address 4-6 regarding who manages the location and whether the individual can access/manage them or not as there is no existing knowledge on this.

1. Specify location as Home which is a Private and Personal place, and which itself may have more information such as postal addresses.
2. Specify location as Work which is Private place, and which can have multiple offices all of which would come under it.
3. Specify location as Device where some information is stored in virtual folders within a specific device's storage, and which is managed by the User.
4. Specify location as App where some information is stored within a software and is managed by that software. Additionally, specify that the app's storage is within the device storage, but is not accessible to the user.
5. Specify location as Browser for Cookies which are set by visiting the internet by Service Provider and Third Parties. These are accessible to the user, but are set by the websites. Here the distinction is that the user can see and interact with the cookies, but they do not have control over the 'location' beyond this.
6. Specify location as asked by a Browser or App where the user can specify their Current Location or their Local Area or City or Region or Country.
7. Specify location as a shop which is open to the public and is monitored by a CCTV.
8. Specify location as a shopping mall which has common areas for sitting etc. and shops which are privately owned but can be visited by the public, and admin areas which are not open to the public.