@foolip, PTAL.

If you want to rename https://github.com/w3c/web-platform-tests/tree/master/generic-sensor as well in this same PR, that'd be fine I think.

Sure, I will do that.

Build PASSED

Started: 2018-03-07 07:10:55
Finished: 2018-03-07 07:43:42

Failing Jobs

• safari:11.0
• MicrosoftEdge:16.16299

View more information about this build on:

• WPT PR Status
• TravisCI

LGTM

@foolip, @lukebjerring, I revisit the introduction guide at http://web-platform-tests.org/introduction.html to confirm how to define directories.

For W3C specs, these directories are typically named after the shortname of the spec (i.e. the name used for snapshot publications under /TR/)

So, we should use the shorname of publications under /TR/ rather than ED spec.
For Generic Sensor, its publication is https://www.w3.org/TR/generic-sensor/

PTAL, I suppose this will affect the code in auto-sync tool.

@foolip, @lukebjerring, friendly ping.

Hmm, so the rename has already happened now. I didn't realize the TR name is different, that seems annoying, and certainly for the purposes of auto-updating IDL it's simpler to pick a name based on the URL we're getting the IDL from rather than where a snapshot might live.

@jgraham @gsnedders what do you think about this? What should http://web-platform-tests.org/introduction.html#test-layout say, and should we do anything about cases that don't match what it says?

My preference is the IDs in https://github.com/foolip/day-to-day/blob/gh-pages/specs.json, because I've picked my favorite ones across the board :)

@foolip so I'm pretty sure it says the TR name because the TR name tends to be far more stable; I don't really have any strong preference but I'd rather not move things around too often.

I guess I think that once something has a TR name, then the github.io name should never change, unless the TR name changes as well. I think there are a few more mismatched cases like this, but I'm not going to go looking for them and seek to unify.

Unless someone notices, I guess leave this one as sensors?

Another instance of Battery Status API:

Latest published version:
http://www.w3.org/TR/battery-status/
Latest editor's draft:
https://w3c.github.io/battery/

IMO, an update for test suite directory will affect many referenced link in corresponding spec documentations(spec, wiki, WG charter). I'd prefer leave it as TR name.

I'm happy to leave that one alone too.

I'm happy to leave that one alone too.

Which one? Battery Status API?
Whatever we choose TR name or github.io name, we should definitely document the rule on http://web-platform-tests.org/introduction.html#test-layout

A few more mismatched cases, but not all:

Latest published version: https://www.w3.org/TR/mediacapture-streams/
Latest editor's draft: https://w3c.github.io/mediacapture-main/
Latest published version: https://www.w3.org/TR/appmanifest/
Latest editor's draft: https://w3c.github.io/manifest/
Latest published version: http://www.w3.org/TR/screen-capture/
Latest editor's draft: https://w3c.github.io/mediacapture-screen-share/
Latest Published Version: https://www.w3.org/TR/orientation-event/
Latest Editor's Draft: https://w3c.github.io/deviceorientation/

Yep, mediacapture-streams vs. mediacapture-main is a fun mismatch I've stumbled upon many times.

@Honry, can you file an issue about documenting this, adding the policy label? If you have a suggested, you can just send a PR.

Whatever "rule" we have, I think we still need to think critically about whether the names make sense. Just "manifest" for example isn't great, given that we also have tools/manifest/ and, well, the manifest.

@foolip, see #9937