Tim Cappalli

> @jyasskin: It seems important to have an interoperable abuse-reporting system for this, but does this WG have the expertise to develop it? No, and I would argue it is...

@npdoty who enforces this?

Just for clarity > The spec includes a registry for exchange protocols (and document formats) The spec explicitly does not deal with document formats / digital credential formats.

> but the idea that an API designed for presentation of identification credentials can also support class-membership proofs is unrealistic in my mind. This is already possible today via FedCM...

I don't think this is necessary as term definitions don't typically link to where they're used. It should be the opposite (the table headings link down to the definitions).

@mohamedamir reversed them in https://github.com/w3c-fedid/digital-credentials/pull/236/commits/92da6972ec74a3f9174cd328150fe3f4443e930d

@marcoscaceres on the last call, you made some comments about the security section not being needed as the spec should be "secure by default". Was your recommendation to remove the...

Removing cgr1-blocker as initial text was added in #189. Leaving open as we still have work to do.

@anthonymkz have you seen HA 2025.8.3 barf on the git URL? ``` Logger: homeassistant.util.package Source: util/package.py:63 First occurred: 14:04:53 (2 occurrences) Last logged: 14:04:55 Invalid requirement 'git+https://github.com/anthonymkz/smartrent-py.git' ```

I think this is better suited for developer docs than the spec (e.g. digitalcredentials.dev). We could just remove: > "supports implementing cross-device experience with proximity checks."