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

Manage shortname change #11

dontcallmedom opened this Issue Oct 10, 2018 · 2 comments


None yet
2 participants

dontcallmedom commented Oct 10, 2018

The proposed new translation workflow proposes to create repository names for translations based on the shortname of the spec under translation.

But these shortnames can change - the translation workflow should accommodate for that possibility.


This comment has been minimized.

StefanSTS commented Oct 11, 2018

Hello Dom,

are we talking about names and "folders" like


Having a repository for REC-rdfa-core-20120607 will be fine. Sorting it by year like it's done until now will keep the folder structure a bit easier to overlook.


Sorting it via technology area might be not so quickly to find.

That the names changes from CR, PR and so on should be fine.
Having it like
would make it easier to sort by technology, but I guess there are other nice filtering methods.


This comment has been minimized.


dontcallmedom commented Oct 12, 2018

I was talking about the names of the github repositories where the translations would be hosted. My current thinking is that they would be à la "" (i.e. non dated) - the linkage to a specific dated version would be managed separately.

Likewise, my expectation is that in most cases, people wouldn't go through github to find the relevant repo (or translation), but would instead use the translation page we're working on rebuilding in W3C. That translation page would indeed provide different filtering methods (with details still TBD)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment