Merge timeOrigin into Level 2

[igrigorik]

Per discussion in [1], merging timeOrigin back into Level 2 and dropping
Level 3. We'll need to republish new CR.

[1]
https://lists.w3.org/Archives/Public/public-web-perf/2017Jul/0010.html

---

Preview | Diff

[siusin]

LGTM except for a minor fix.

[siusin]

No need to change the specStatus here...

The auto-pub system will stop working once we re-publish the CR and drop Level 3. The group is encouraged to maintain the future changes in the editor's draft (w3c.github.io/hr-time/) . The process to update the CR for future editorial changes is pretty simple, although it's not allowed in the auto-pub system yet. Please ping plh or me for the future hr-time publication when needed.

[siusin]

Thanks @igrigorik .

I'll start the CR update transition, and publish the Level 3 as a WG-NOTE (the group can revive it as a WD any time in the future).

[igrigorik]

@siusin reverted specStatus. Re, your comment above, to confirm that I'm following:

• You'll republish L3 as a note; we should add a disclaimer that it's not actively worked on and developers should refer to L2?
• One this PR lands, the L2 status is back to ED and it will republish automatically, right?
  • Once we agree to move L2 to CR (again), you'll publish manually.

Does that sound about right?

[siusin]

@igrigorik thanks!

re L3,

• yes, we will also make /TR/hr-time point to /TR/hr-time-2.

re L2,

• w3c.github.io/hr-time/ will be the editor's draft of L2, once we merge this PR, it'll be updated automatically by GitHub whenever people commit to the repo.
• /TR/hr-time-2 will point to the new CR of L2, if the group wants to make changes to the document at /TR/hr-time-2 in the future, I'll publish a new CR manually.

Does it make sense?

[igrigorik]

yes, we will also make /TR/hr-time point to /TR/hr-time-2.

Great!

w3c.github.io/hr-time/ will be the editor's draft of L2, once we merge this PR, it'll be updated automatically by GitHub whenever people commit to the repo.

Yep, confirmed: https://w3c.github.io/hr-time/

/TR/hr-time-2 will point to the new CR of L2, if the group wants to make changes to the document at /TR/hr-time-2 in the future, I'll publish a new CR manually.

TR is pointing to old (Nov 2016) draft. You'll republish new ED version as CR?

[siusin]

TR is pointing to old (Nov 2016) draft. You'll republish new ED version as CR?

Yes, we'll need a Director's approval this time because we are updating an existing Candidate Recommendation with substantive changes, which may take several days. For the future editorial changes, we just need to send a publication-request and update the CR directly.

[igrigorik]

Gotcha, makes sense. I think we're all set then. Let's get the CR republished, and on the next call we can discuss what the next steps are for moving this spec forward.

/cc @toddreifsteck fyi.