W3C Bot

Results 229 comments of W3C Bot

This was discussed during the [#json-ld meeting on 09 April 2025](https://www.w3.org/2025/04/09-json-ld-minutes.html#d2f7). View the transcript w3c/json-ld-syntax#443 <gb> Issue 443 `@protected` creates unresolvable conflicts when the same term is defined in two...

This was discussed during the [#did meeting on 06 December 2024](https://www.w3.org/2024/12/06-did-minutes.html#d880). View the transcript w3c/did-core#802 decentralgabe: This is another one that was covered in the VCWG in the controllable identifier...

[pchampin](https://github.com/pchampin) marked as non substantive for IPR from ash-nazg.

This was discussed during the [#did meeting on 06 December 2024](https://www.w3.org/2024/12/06-did-minutes.html#d1e2). View the transcript w3c/did-core#539 manu: +1 to closing, the current process is to raise an issue, discuss in WG,...

This was discussed during the [#did meeting on 27 March 2025](https://www.w3.org/2025/03/27-did-minutes.html#a733). View the transcript w3c/did#539 ottomorac: This issue is clean up herd privacy issue. Manu suggested closing this Wip: lets...

[mehmetoguzderin](https://github.com/mehmetoguzderin) marked as non substantive for IPR from ash-nazg.

This was discussed during the [#did meeting on 06 December 2024](https://www.w3.org/2024/12/06-did-minutes.html#7cc1). View the transcript w3c/did-core#821 manu: The group should discuss this, maybe special topic call? decentralgabe: Yes, special topic call.

This was discussed during the [#did meeting on 08 May 2025](https://www.w3.org/2025/05/08-did-minutes.html#6967). View the transcript 821 - Ambiguity regarding PATH and DID URLs <ottomorac> w3c/did#821 ottomorac: This was discussed a few...

[lukewarlow](https://github.com/lukewarlow) marked as non substantive for IPR from ash-nazg.

This was discussed during the [#did meeting on 21 August 2025](https://www.w3.org/2025/08/21-did-minutes.html#a824). View the transcript Define how DID Methods can specify paths and their dereferencing rules #156 <ottomorac> w3c/did-resolution#156 <ottomorac> Issue...