search

w3c / vc-wg-charter

Developing a new charter for the VC WG.
https://w3c.github.io/vc-wg-charter/
Other
3 stars 12 forks source link

This should be LEVEL 2 not VERSION 2 #81

Closed nadalin closed 2 years ago

nadalin commented 2 years ago

W3C updates go by LEVEL, if this is truly an update to the previous VC specification this should be LEVEL 2 and called out in the charter.

iherman commented 2 years ago

There is no such hard rule at W3C, @nadalin (maybe there should be, but that is another discussion). Working groups have the freedom to use other terminology like "version". There are several examples; see, for example, the EPUB WG Charter (where I am also active) which uses the term "version" all over the place.

OR13 commented 2 years ago

Suggest we close the issue in absence of a citation.

Breaking changes implies a version change to me.

peacekeeper commented 2 years ago

I think "level 2" sounds like it's a superset or an additional layer on top of "level 1", which would be confusing. So "version" seems like a better term.

nadalin commented 2 years ago

This brings up the question of version 2 supercedes Verizon 1 or are both still viable. Level seems a better term, that could be why W3C recommends that term.

Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Markus Sabadello @.> Sent: Wednesday, March 2, 2022 12:42:41 PM To: w3c/vc-wg-charter @.> Cc: Anthony Nadalin @.>; Mention @.> Subject: Re: [w3c/vc-wg-charter] This should be LEVEL 2 not VERSION 2 (Issue #81)

I think "level 2" sounds like it's a superset or an additional layer on top of "level 1", which would be confusing. So "version" seems like a better term.

— Reply to this email directly, view it on GitHubhttps://github.com/w3c/vc-wg-charter/issues/81#issuecomment-1057358500, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB4R4YZQEF5HVS4WI7WFVSLU57HEDANCNFSM5PFHN7PA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.***>

iherman commented 2 years ago

This brings up the question of version 2 supercedes Verizon 1 or are both still viable. Level seems a better term, that could be why W3C recommends that term.

W3C does not "recommend" that term. WG-s choose (or not) that term or use a different one. It is the prerogative of a WG.

iherman commented 2 years ago

The issue was discussed in a meeting on 2022-03-02

View the transcript #### 5.2. This should be LEVEL 2 not VERSION 2 (issue vc-wg-charter#81) _See github issue [vc-wg-charter#81](https://github.com/w3c/vc-wg-charter/issues/81)._ **Brent Zundel:** next issue #81. … rather than v2, perhaps we should call it level 2 to comply with other W3C recommendations. **Manu Sporny:** there's no rule in here that says use level 2 instead of version 2. It is confusing. > *Joe Andrieu:* -1 on this issue. **Joe Andrieu:** Level 2 to me, implied semantics, seems to me that Level 1 is still valid. It doesn't convey we're "updating that first version to newer version, where not all of the first thing might be valid anymore.". > *Juan Caballero:* "An earlier version of EPUB (EPUB 3.0.1) was published as an ISO standard ISO/IEC TS 30135:2014 (parts 1-7). This Working Group and ISO may consider updating that ISO specification once the new Recommendations are published..." > Additionally, there are currently activities within ISO/IEC JTC 001/SC34 on specifications that rely on earlier versions > of EPUB (e.g., EPUB Preservation, EPUB Accessibility). A liaison has to be maintained on, possibly, updating those ISO specifications to the latest versions of EPUB 3, specified by this Working Group." > *Juan Caballero:* (^from Iván's example).
nadalin commented 2 years ago

I find use of version very confusing not knowing if version 2 supercedes or both versions are valid. Whatever naming is used. It needs to be clarified on the intent on this next version or level.

Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Ivan Herman @.> Sent: Thursday, March 3, 2022 1:58:06 AM To: w3c/vc-wg-charter @.> Cc: Anthony Nadalin @.>; Mention @.> Subject: Re: [w3c/vc-wg-charter] This should be LEVEL 2 not VERSION 2 (Issue #81)

The issue was discussed in a meetinghttps://www.w3.org/2017/vc/WG/Meetings/Minutes/2022-03-02-vcwg#section5-2 on 2022-03-02

View the transcript 5.2. This should be LEVEL 2 not VERSION 2 (issue vc-wg-charter#81)

See github issue vc-wg-charter#81https://github.com/w3c/vc-wg-charter/issues/81.

Brent Zundel: next issue #81https://github.com/w3c/vc-wg-charter/issues/81. … rather than v2, perhaps we should call it level 2 to comply with other W3C recommendations.

Manu Sporny: there's no rule in here that says use level 2 instead of version 2. It is confusing.

Joe Andrieu: -1 on this issue.

Joe Andrieu: Level 2 to me, implied semantics, seems to me that Level 1 is still valid. It doesn't convey we're "updating that first version to newer version, where not all of the first thing might be valid anymore.".

Juan Caballero: "An earlier version of EPUB (EPUB 3.0.1) was published as an ISO standard ISO/IEC TS 30135:2014 (parts 1-7). This Working Group and ISO may consider updating that ISO specification once the new Recommendations are published..." Additionally, there are currently activities within ISO/IEC JTC 001/SC34 on specifications that rely on earlier versions of EPUB (e.g., EPUB Preservation, EPUB Accessibility). A liaison has to be maintained on, possibly, updating those ISO specifications to the latest versions of EPUB 3, specified by this Working Group."

Juan Caballero: (^from Iván's example).

— Reply to this email directly, view it on GitHubhttps://github.com/w3c/vc-wg-charter/issues/81#issuecomment-1057873682, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB4R4Y3UFGJC2WSVGGBIEGDU6CEK5ANCNFSM5PFHN7PA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.***>

Sakurann commented 2 years ago

We added a following text to the charter to clarify that version 2 supersedes version 1:

It is explicitly not a requirement that the new specifications be fully compatible with related past specifications.

Would this be acceptable?

nadalin commented 2 years ago

LGTM

brentzundel commented 2 years ago

closing, based on discussion in the group meeting

iherman commented 2 years ago

The issue was discussed in a meeting on 2022-03-16

View the transcript #### 4.1. This should be LEVEL 2 not VERSION 2 (issue vc-wg-charter#81) _See github issue [vc-wg-charter#81](https://github.com/w3c/vc-wg-charter/issues/81)._ **Kristina Yasuda:** I think it turned out that Tony's concern was that version 2 allows breaking changes to version 1. That it supersedes version 1 and we already have that in the charter and he's ok with that language. … So we can close that issue. **Manu Sporny:** That does not mean that our intent is to completely break VCs. There should be an expectation that any backwards compatible or breaking change will undo significant scrutiny. > *Michael Prorock:* +1 manu - avoiding breaking changes if possible. **Kristina Yasuda:** I think the clarification here is that we will tell people to look at version 2 once published. **Manu Sporny:** Correct. **Kristina Yasuda:** Yes, and we aren't actively trying to break version 1 if we can avoid it.