Closed iherman closed 3 weeks ago
I agree with this.
@iherman can you please create a PR for this? Thanks.
The problem comes from the very last paragraph of § Contexts as Vocabularies that refers to the VCDM spec on processing JSON-LD contexts and vocabularies further. Although informative (is that o.k., b.t.w.?) it refers to major sections in the VCDM, so a dependency is established.
I actually wonder whether the issue is much more complex than I realized at first. Looking at the section as a whole, it describes references to vocabularies, content digests, etc, that are all VCDM specific. I am not sure that is appropriate for this document, which should probably stay more generic. At the minimum, the corresponding DID information should also be added to the document.
This must be extensively discussed before raising a PR.
cc @msporny
This must be extensively discussed before raising a PR.
We discussed this during the call this week. The conclusion was that we could remove most, but not all of the VCDM references. If we wanted to remove all of the VCDM references, we'd end up having to remove sections that specifically talk about specifications that build on top of the Controller Document specification.
IOW, the issue is more complex than it seemed at first. We can attempt a PR to clean things up, but removing the reference is probably not going to work unless we also want to get into a discussion about removing privacy/security considerations sections that were requested during DID Core review (which would be a significant change... we would then need to go back to the reviewers that asked for those sections and ask them if they are fine w/ the new formulation -- which I doubt they'd be, given that we're removing sections they specifically asked for).
The issue was discussed in a meeting on 2024-07-31
@msporny indeed, this is more complex than it seemed. I may be fine keeping some VC references but, then, we should have references to the DID spec as well (when applicable). I know this document is aimed at a larger audience but, at least for now, one of its primary purposes is to make a bridge between those two...
I am looking forward to the PR.
PR #82 has been raised to address this issue. This issue will be closed once PR #82 has been merged.
PR #82 has been merged, closing.
I was wondering how the VCDM reference landed in the list of formal references (although only as informal). I did not see any trace of it in the text itself...
It would be probably "cleaner" if that reference didn't appear there.