W3C Bot

Results 227 comments of W3C Bot

This was discussed during the [#did meeting on 27 February 2025](https://www.w3.org/2025/02/27-did-minutes.html#780b). View the transcript w3c/did-resolution#95 Minimizing the extent of profiling of requestors #95 wip: is there an action on this one?...

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

This was discussed during the [#did meeting on 19 December 2024](https://www.w3.org/2024/12/19-did-minutes.html#775b). View the transcript w3c/did-core#860 manu: this one is also for you, Wip :) … The W3C TAG raised an...

This was discussed during the [#did meeting on 08 May 2025](https://www.w3.org/2025/05/08-did-minutes.html#8e91). View the transcript 884 - DID needs a proper vocabulary specification <ottomorac> w3c/did#884 ottomorac: We need a vocabulary for...

This was discussed during the [#did meeting on 29 May 2025](https://www.w3.org/2025/05/29-did-minutes.html#1082). View the transcript w3c/did#892 Wip: I want to give Ivan some time to discuss this. Ivan: There's not too...

This was discussed during the [#did meeting on 24 April 2025](https://www.w3.org/2025/04/24-did-minutes.html#0523). View the transcript Should we use JSON or JSON-LD for the resolution spec? <ottomorac> w3c/did-resolution#137 ottomorac: Briefly touched on...

This was discussed during the [#did meeting on 15 May 2025](https://www.w3.org/2025/05/15-did-minutes.html#9d17). View the transcript Should we use JSON or JSON-LD for the resolution spec? <Wip> w3c/did-resolution#137 wip: wonder where we...

This was discussed during the [#did meeting on 15 May 2025](https://www.w3.org/2025/05/15-did-minutes.html#8c49). View the transcript w3c/did-resolution#18 <Wip> w3c/did-resolution#17 Clarify the role of the DID Resolution spec relative to other DID specs #18...

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

This was discussed during the [#did meeting on 10 July 2025](https://www.w3.org/2025/07/10-did-minutes.html#00db). View the transcript Model accept as the HTTP accept header #116 <ottomorac> w3c/did-resolution#116 ottomorac: The was a suggestion from...