You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are changes coming to references with JSON 5 and containers. Once JSON 5 is in production, review and potentially revamp some aspects of references.
Allow non-authors to modify entries, specifically to add references, possibly using containers, possibly as ADPs. We've discussed an ADP pilot for this. Limiting content/reference updates to ADPs will probably prevent useful content/reference updates (from the vast majority of potential content providers who are not ADPs). Maybe an ADP could act as a clearinghouse for non-ADP reference submissions?
What happens to the old reference maps? Is CONFIRM (official vendor reference) required? Is everything just a URL?
There are changes coming to references with JSON 5 and containers. Once JSON 5 is in production, review and potentially revamp some aspects of references.
Allow non-authors to modify entries, specifically to add references, possibly using containers, possibly as ADPs. We've discussed an ADP pilot for this. Limiting content/reference updates to ADPs will probably prevent useful content/reference updates (from the vast majority of potential content providers who are not ADPs). Maybe an ADP could act as a clearinghouse for non-ADP reference submissions?
What happens to the old reference maps? Is CONFIRM (official vendor reference) required? Is everything just a URL?
See CVE IDs really need structured inter/intra-ID relationships, as noted in 1999 #10