search

w3c / webappsec-mixed-content

WebAppSec Mixed Content
https://w3c.github.io/webappsec-mixed-content/
Other
12 stars 22 forks source link

Remove TR reference from MIX2 #49

Closed carlosjoan91 closed 3 years ago

carlosjoan91 commented 3 years ago

As mentioned in #25, the "Last Published Version" link in MIX2 currently leads to a 404, since there is none (as MIX2 is still only an Editor's Draft). This removes the link, which we can re-add once MIX2 moves to FPWD and there is a published version to point to.

carlosjoan91 commented 3 years ago

annevk: Can you please also review this small change? Thanks.

sideshowbarker commented 3 years ago

I wonder if we could simply replace mixed-content and not introduce mixed-content-2, especially with the new process coming soonish.

We would first want to transition mixed-content out of CR and on to Rec. After that, I think we could effectively replace it with document that uses the new process.

carlosjoan91 commented 3 years ago

I wonder if we could simply replace mixed-content and not introduce mixed-content-2, especially with the new process coming soonish.

Looking at the new process, that sounds good to me since MIX2 will obsolete MIX anyways. I'll bring this up in the next meeting. (also cc @mikewest as editor of MIX, in case they have objections).

We would first want to transition mixed-content out of CR and on to Rec. After that, I think we could effectively replace it with document that uses the new process.

With the (big) caveat that I might be misunderstanding the new process, wouldn't replacing MIX with MIX2 while MIX is at CR fall under https://www.w3.org/wiki/Process2020#Updating_Candidate_Recommendations ? The "Periodically (not more than twice a year, to avoid aggravating the lawyers and the AC)" language in the "Updating Recommendations" section makes me think it would be more desirable to have MIX2 replace MIX before moving to Rec instead of moving to Rec if we know changes will come soon.

(In either case, I'll go ahead and merge this for now, to remove the 404 link while we have a TR to link to).

sideshowbarker commented 3 years ago

With the (big) caveat that I might be misunderstanding the new process, wouldn't replacing MIX with MIX2 while MIX is at CR fall under w3.org/wiki/Process2020#Updating_Candidate_Recommendations ?

I’m honestly not sure. I have to admit that — despite reading the documentation about it — I don’t yet understand the new process well enough myself to be able to say. I think with the old process, if we made substantive/normative changes to a spec while it was at CR, then we had to restart the CR process. Since the current Mixed Content CR was published before new process started, I don’t know whether that means we’d need start the CR process again if we folded the Mix2 changes into it.

I’ve already suggested this be put on the agenda for the WebAppSec telcon this week — so if you’re able to attend that, it would be a good opportunity to discuss it.

The "Periodically (not more than twice a year, to avoid aggravating the lawyers and the AC)" language in the "Updating Recommendations" section makes me think it would be more desirable to have MIX2 replace MIX before moving to Rec instead of moving to Rec if we know changes will come soon.

That seems like a question to take to the working group to make. I think whatever ends up happening with this, it needs to be a working-group decision. So, the chairs would need to announce a CfC and all that. But I think the best place to start would be by having a synchronous discussion about it in real time together on the WebAppSec telcon this week.

carlosjoan91 commented 3 years ago

Yeah, I agree that discussing the way forward in the next meeting would be good. As I mentioned on the previous comment, I'm planning to bring this up there (and was planning to PR into the agenda once it was up, but I see it's already included now that it's up), so I am indeed planning to attend.