Re: Microformats and logical URLs -- mod_rewrite

[Victor Engmark]

On 4/23/07, Davi Leal <address@hidden> wrote:

So, it seems that using mod_rewrite is even convenient. It makes it easier to
define the logical URLs. What I propose now is:

   physical URLs:      *.php

   logical URLs:       /tag

I think the Klaus' architecture should take all this into account. And as
Victor exposed, it could be easy add this mod_rewrite layer to the current
webapp at production. What do you think?

*Nodding vigorously*

The logical-physical URLs relation which I propose is:

  https://gnuherds.org/Home.php
                      /home

I think this should just be http://gnuherds.org/ - There's no reason to "waste" the root URL.

  https://gnuherds.org/Timeline.php
                      /news or /timeline ???

Depends on whether the suggestion to move the data into a separate news page is followed through.

  https://gnuherds.org/GNU_Herds_Hackers_Guide.php
                      /guide ???

Some suggestions, with bookmark count from del.icio.us:

• /dev - 3 chars, 72,661 bookmarks.
  
• /develop - 7 chars, 306,731 bookmarks
  
• /developers - 10 chars, 39,272 bookmarks
• /development - 10 chars, 362,766 bookmarks
• /hack - 4 chars, 98,211 bookmarks
• /hackers - 7 chars, 9,126 bookmarks

Surprising results, with "development" coming in first, at about 20% more than "develop". I guess we should use that.

  https://gnuherds.org/FS_Business_Networks.php
                      /business or business_networks  ???

After having a look at the page, I believe the current name is misleading. It's just a collection of links to sites related the same kind of activity GNU Herds does. I'd use "/links" for that page.

  https://gnuherds.org/e-Voting_SIG.php
                      /evote ???

This could be part of a general FAQ. It looks as though a lot of the content could be removed:

• The links from the "Bringing free software to voting booths" article; just link to the article itself, if necessary.
• GNU.FREE is linked twice.
• Do we really need the link to the "IEEE Voting Equipment Standards"?

A short description of how the system works should IMO be enough.

  https://gnuherds.org/Lost_Password.php
                      /lost_password ???

/password, maybe? I don't think that's likely to ever be used for anything else.

  https://gnuherds.org/Person.php
                      /person

  https://gnuherds.org/Company.php
                      /company

  https://gnuherds.org/non-profit_Organization.php
                      /nonprofit

All these should IMO be at "/register", with a single link from the front page, as discussed.

  https://gnuherds.org/View_Job_Offer.php?JobOfferId=XXX
                      /view_job_offer?JobOfferId=XXX  ???

If you move FS_Job_Offers.php to /jobs, this could just be "/jobs?id=XXX". Like Google's "/search?q=search+terms".

  https://gnuherds.org/Qualifications.php
                      /qualifications

How about /experience? That's the word used by the hResume microformat.

  https://gnuherds.org/Manage_Job_Offers.php
                      / ???

How about "/jobs?owner=me"?

  https://gnuherds.org/View_Job_Applications_State.php
                      / ???

I suggest "/jobs?applied=yes".

  https://gnuherds.org/Job_Offer.php?JobOfferId=XXX
                      /offer or /joboffer ???

Is this different from View_Job_Offer.php?

  https://gnuherds.org/Manage_Job_Offer_Applications.php?JobOfferId=XXX
                      / ???

I suggest "/jobs?action=""

  https://gnuherds.org/View_Qualifications.php?EntityId=XXX
                      /view_qualifications?EntityId=XXX

How about just "/qualifications?id=XXX"?

The general idea of the suggested URLs is that each type of object has its own path (
e.g., "/jobs"), and different parameters to define actions (e.g., "?action="" and filtering (e.g., "?id=XXX" and "?applied=yes").

-- 
Victor Engmark
Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound