Gervase Markham wrote:
> 
> One side effect of chopping off extensions is that it's not immediately
> obvious in discussion what is a file and what is a folder. Can we all
> take care to refer to folders with a trailing slash? Thanks :-)
> (i.e. /mozilla/foo is a document foo in folder mozilla; mozilla/foo/ is
> a folder foo in folder mozilla, and accessing that url gives you
> mozilla/foo/index_html)

Well, everything is potentially a folder (that's the advantage of
dropping file extensions ;) but I'll try to remember to drop the
slash when referring to the index document.

> You can't move the directories when the releases get old, so you have
> to have a flat system like:
> 
> /mozilla/releases/0.6
> ...
> /mozilla/releases/0.9.3
> 
> If that's true, and you don't want to list all the old releases on the
> document mozilla/releases/(index_html) , then you need another document
> which is a long list of the old ones. /mozilla/releases/archive seems
> like a good name for it.
> 
> Having said that, I still don't understand your point. Please say
> exactly what your version would look like.

/download_directory (whatever it's named [1])
  |
  |--mozilla/
      |
      |--releases/
      |   |
      |   |--0.6
      |   |
      |   |--0.7
      |   |
      |   |--etc.  
      |
      |--distributions
      |
      |--etc.

Probably looks familiar...

'mozilla' is like http://mozilla.org/releases/ - It describes
Mozilla and links to the latest releases in 'mozilla/releases/'.

'mozilla/releases' is an index of all the releases in the
'mozilla/releases/' directory.

Nothing gets moved when it's old; the link from 'mozilla' to the
latest release just gets replaced with one to the newer release.
However, all releases are _always_ linked from 'mozilla/releases'.
It's like an archive listing except it also has the current
release listed--so it's a complete listing.

The link from 'mozilla' is a navigation detail. It shortcuts the
release listing. The location of the listing, however, is a URI
issue.

Now, applying the hierarchy - walking down to 0.6

  mozilla.org/ - mozilla.org

  download_directory/ - provides general information on
                        Mozilla software products--basically
                        what's available here.

  mozilla/ - provides general information about Mozilla,
             specifically. This includes feature summaries,
             distributions, and, of course, releases.

  releases/ - information in here applies -only- to Mozilla
              releases. It is an index of all the releases;
              thus the parent-child relationship to 0.6/

  0.6 - information here applies just to Mozilla's 0.6
        release. If you walk up from here, you will note
        that information in each ancestor applies to the
        0.6 release, but is more generalized at each step,
        incorporating information about its other children
        as well.

A 'mozilla/archive' in the structure you've posted would be in
a sibling relationship to the individual release directories.
However, the relationship is more accurately expressed as
parent-child, as described above.

Another advantage of this is that you can describe distributions
without labeling them as "mozilla.org/releases". :)

Like articles in the '/news' hierarchy, information in 'releases/'
is in a sort of current archive. As info gets outdated, it
loses prominence in the content and navigation, but it doesn't
move.


The information in this section of mozilla.org lends itself very
well to hierarchical organization. If one were to browse by the
file listing and not the index pages, the path to a given
document would probably be self-evident.


[1] Three possibilities are "download", "products", and "software".
    Can't think of any others atm.

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get your FREE credit report with a FREE CreditCheck
Monitoring Service trial
http://us.click.yahoo.com/MDsVHB/bQ8CAA/ySSFAA/9rHolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 




Reply via email to