Pierre-Antoine Champin

[[ Finally, we object to restrictions on significant breaking changes in DID Core v2.0. The lack of media type coherence in the first version requires fully breaking changes to correct...

> Maintenance charter for DID-core should explicitly document (...) Do you mean "it should be documented *in* the charter" (which is how I read your text literally, or "the charter...

[[ This group at the W3C should focus on the data model, URLs, dereferencing and resolution, not standardization of specific did methods. We object to standardizing any specific DID methods...

From @jandrieu [[ [This charter] includes unnamed DID Methods in scope, which we see as fundamentally undermining the entire point of decentralized identifiers: decentralization. (...) The primary technical objection to...

From @rxgrant [[ While it is appropriate for the W3C to at any time convene WGs to standardize any DID Methods that members find sufficient interest in, this MUST occur...

+1 on this feature request. It is not only useful with conda, but with virtualenv's (or venv's in Python3): * In most of my project, I have a virtualenv configured...

I would also like to see IP addresses allowed in did:web, although I appreciate the issue related to SSL certificates. Another issue I can see if with IPv6 addresses, because...

> will bang on this in the next couple of days. Never write anything like that :smiling_imp: I bumped into the same problem, btw :wink:

+1 On 27/08/2020 16:23, BigBlueHat wrote: > The Chairs and Editors propose that the JSON-LD 1.0 specification > should be marked as superseded by the > JSON-LD 1.1 specification released...

"superceded" and the "outdated" red popup play slightly different roles. * The red popup appears whenever a more recent version of the *same* specification exists. In particular, it appears when...