Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
spec:shortnames [2012/09/05 14:33] – [Unversioned Names] fantasaispec:shortnames [2012/09/06 08:32] – [Versioned Names] Added option c tabatkins
Line 3: Line 3:
 This page is to record our policy for CSS module shortnames going forward and a plan for converting all existing shortnames to match this scheme. A shortname is used as the filename on /TR and dev.w3.org and also as the [spec-code] in www-style discussions. The existing scheme was set up in the 20th century, before the concept of independently-levelling CSS modules was created. This page is to record our policy for CSS module shortnames going forward and a plan for converting all existing shortnames to match this scheme. A shortname is used as the filename on /TR and dev.w3.org and also as the [spec-code] in www-style discussions. The existing scheme was set up in the 20th century, before the concept of independently-levelling CSS modules was created.
  
-==== Unversioned Names ====+===== Unversioned Names =====
  
 Each module will have an unversioned shorname on /TR, which aliases to the latest level. This is identical to the module shortname, except without the number, e.g. ''css-transitions''. (We already have this with /TR/selectors.) Each module will have an unversioned shorname on /TR, which aliases to the latest level. This is identical to the module shortname, except without the number, e.g. ''css-transitions''. (We already have this with /TR/selectors.)
Line 9: Line 9:
 **Issue:** Do we want to set this up on dev.w3.org as well? As alias or redirect? **Issue:** Do we want to set this up on dev.w3.org as well? As alias or redirect?
  
-**Issue:** At what point in the process does the shortname move over?+**Issue:** At what point in the process does the shortname move over to the next level?
   * Option A = CR   * Option A = CR
   * Option B = Snapshot acceptance   * Option B = Snapshot acceptance
   * Option C = REC   * Option C = REC
  
-==== Versioned Names ====+===== Versioned Names =====
  
 Each module will have a versioned shortname on /TR, for accessing a specific level of the module. Currently we use ''cssN-foo'', but don't do this correctly for Level 1 modules like Flexbox. Each module will have a versioned shortname on /TR, for accessing a specific level of the module. Currently we use ''cssN-foo'', but don't do this correctly for Level 1 modules like Flexbox.
Line 23: Line 23:
   * Republishing at ''css1-foo''   * Republishing at ''css1-foo''
   * Setting up a temporary redirect from ''css3-foo'' to ''css1-foo'' until the module reaches level 3.   * Setting up a temporary redirect from ''css3-foo'' to ''css1-foo'' until the module reaches level 3.
 +  * Unsolicited feedback from several authors indicates that this pattern is confusing, because of the connection with general "CSS3" messaging.
  
 == Option B == == Option B ==
Line 29: Line 30:
   * Moving all specs to ''css-fooN''   * Moving all specs to ''css-fooN''
   * Setting up permanent redirects from ''css3-foo'' to ''css-fooN''   * Setting up permanent redirects from ''css3-foo'' to ''css-fooN''
 +  * This model is already used by Selectors, and several WebApps specs.
  
 +== Option C ==
 +
 +Slight variation on Option B: follow ''css-foo-N'' pattern. Fix all specs by
 +  * Moving all specs to ''css-foo-N''
 +  * Setting up permanent redirects from ''css3-foo'' to ''css-foo-N''
 +  * This might be more readable.
 
spec/shortnames.txt · Last modified: 2014/12/09 15:48 by 127.0.0.1
Recent changes RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki