I guess what I am saying is: it doesn’t explain the problem it is solving very well. It doesn’t say what the default behavior is for other cards set as transit cards do (I would expect it to work the same way-ish) and how transit providers are supposed to match people to tickets, etc. then why this particular card is special. It assumes you know.
That whole "The solution" section does explain this.
"what the default behavior is for other cards set as transit cards" statement is countered by the article "Your device stops randomizing the UID on each tap". Granted, I know this part because in the past Google Pay on Android would randomize the UID on each read and on Apple devices transferring cards between devices would reinitialize the UID but would keep some application-specific (like a Suica card identifier) static, thus making these virtual cards unsuitable for UID-based identification for access control.
"how transit providers are supposed to match people to tickets" is not relevant to the premise of "This repository describes general status on the topic and a possible solution to allow you to use your device as an access card in UID-based access systems." In general, these are stored fare cards so they do not store a ticket and instead store an available balance.
