Tobie Langel

@nigelmegitt to clarify my position here, handling versions and editions is an automated way in Specref is a lot of work that I'm not expecting anyone to feel like doing...

> further work would be needed, perhaps in backend tooling, to populate the title shown in specref with the unqualified (no subtitle) one for generic spec URLs and the qualified...

Can you explain what that would change?

Oh, so we hit the server everytime no matter what?

Thanks. What's your timeline for this and would you have resources to implement those changes in Specref?

I looked at this a bit, and it's a significant amount of work as W3C's API doesn't appear to be designed for this use case. I don't have the resources...

Things to think about: - Updates are hourly, we risk going above the threshold allowed by the API. - We need to go through all specs every hour to see...

The latter.

> For sure! That said, I don't know what legal or other structural considerations to think about when designing those tools at this time. This is regularly done by the...

Additionally: * Have work contracts which makes it easy for developers to work on open-source on their own time and on their work computer while retaining their rights. * [Open...