LWS WG meeting 2025-06-21 - "levels" of portability

Dear LWS WG,


to follow up on last meetings (2025-06-23) discussion on portability 
"levels" [1].
The proposed levels can be viewed through a functional and 
non-functional lens.

Functional Capabilities:
Levels 0 (resource transfer), 1 (auxiliary resources transfer), and 3 
(authorization preservation) describe what the system should be able to do.

Non-Functional Requirement:
Level 2 ("preservation of user experience") describes a desired quality 
or outcome of the system's operation.

Therefore, I suggest we treat "user experience" not as a numbered level 
in a sequence, but as a non-functional requirement that applies to the 
entire topic of portability.


A particular use case is the end-user process of moving a bank account.
A new bank typically offers a service to:
     - automatically transfer the balance and regular payment plans
     - notify anyone who regularly sends money to the old account
     - close the old account
It is common for the user to have to re-authorize third-party apps to 
access details at the new account.
 From the end-user's perspective, the success of this process is 
measured by the functional outcome.
How good of an experience it is, is a qualifying property of the outcome.


A follow up question on the functional levels:
Would Level 1 ("transferring metadata" like auxiliary resources, ACLs) 
already include "preserving authorization" (Level 3), since ACLs are 
mentioned?

My explicit assumption for Level 1 would be that for the transfer to be 
effective, auxiliary resources are not only copied to the new location 
but are also kept in sync to reflect the move of the primary resource.


Cheers
Christoph

[1] https://www.w3.org/2025/06/23-lws-minutes.html

Received on Wednesday, 25 June 2025 11:38:29 UTC