Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Respec's "Latest published version" #46

Closed
patrickhlauke opened this issue Mar 17, 2016 · 7 comments

Comments

Projects
None yet
3 participants
@patrickhlauke
Copy link
Member

commented Mar 17, 2016

Looking at https://w3c.github.io/pointerevents/, respec currently generates the following

Latest published version:
http://www.w3.org/TR/pointerevents-level-2/
Latest editor's draft:
https://w3c.github.io/pointerevents/
Latest Recommendation:
http://www.w3.org/TR/pointerevents

Obviously, the "Latest published version" URL currently 404s. Anybody versed enough in the dark arts of respec know how this can be fixed (taking inspiration, perhaps, from the markup used for http://w3c.github.io/touch-events/) ?

@patrickhlauke

This comment has been minimized.

Copy link
Member Author

commented Mar 17, 2016

Just changing

shortName:            "pointerevents-level-2",

to

shortName:            "pointerevents",

would do the job, but is it...semantically correct?

@RByers

This comment has been minimized.

Copy link
Contributor

commented Mar 29, 2016

IIRC @jacobrossi and I discussed this when the spec was renamed. I think the conclusion was that leaving it as-is was semantically correct, despite the broken link (there have not been any "published" versions of "pointer events level 2" yet). Should be able to find the history of this discussion somewhere....

@patrickhlauke

This comment has been minimized.

Copy link
Member Author

commented Mar 29, 2016

wondering then if there's some extra setting/incantation in respec to suppress the "latest published version" ... some way of saying that at this stage there's only an editor's draft, and no actual published version. i'm sure there must be something...

@shepazu

This comment has been minimized.

Copy link
Member

commented Mar 29, 2016

We could solve this by doing a FPWD for http://www.w3.org/TR/pointerevents-level-2/.

Do we think we could do this sometime soon?

@patrickhlauke

This comment has been minimized.

Copy link
Member Author

commented Mar 29, 2016

@shepazu

Do we think we could do this sometime soon?

If you let me know what's needed, from an organisational standpoint, my gut feeling would be that we could... (he said naively)

@shepazu

This comment has been minimized.

@patrickhlauke

This comment has been minimized.

Copy link
Member Author

commented Jun 13, 2016

Closing, as this will be resolved as soon as the FPWD is published

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.