Re: Microformats and logical URLs -- mod_rewrite

[Davi Leal]

Victor Engmark wrote:

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

I have already modified it at production. Now the Home link of the menu link 
to  https://gnuherds.org/  instead of  https://gnuherds.org/Home.php



> >   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.

The current Timeline page is separated.  Move what data?



> >   https://gnuherds.org/GNU_Herds_Hackers_Guide.php
                          /development

> 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.

No, those activities are not carried out by GNU Herds. They are business 
networks or ways to set up one, which we know about. Maybe we should use 
something as     /business_network_models  ?



> >   https://gnuherds.org/e-Voting_SIG.php
> >                       /evote ???
>
> This could be part of a general FAQ.

Yes, but moving it, we will get an empty o removed "Special Interest Groups" 
section. Maybe it is convenient. I am not sure.

Anyway, what question will answer?.  "What e-Voting system will use GNU 
Herds?". Maybe it could be placed below this one: "How is the Job Site module 
related to the GNU Herds Association?".

What do you think?



> 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.
It is good we link to the reference from where we have take the information. 
Isn't?

>    - GNU.FREE is linked twice.
I have removed it.

>    - Do we really need the link to the "IEEE Voting Equipment Standards"?
I have removed it.

Let me know any additional modification which must be realized!.



> >   https://gnuherds.org/Lost_Password.php
                          /password



> >   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 .

This will take some work. Therefore it will not be so easy add this to 
production. First we will have to fix this kind of thing.  Anyway, I like how 
directly you get an specific form for fill all the Person, Company or 
non-profit data.

It could be good be able to see this proposal working, before taking a 
decision. So we will able to compare it.  You know, merging it in a register 
page will get extra click to finish a registration. Maybe we have to think 
more about this?.



> >   https://gnuherds.org/View_Job_Offer.php?JobOfferId=XXX
                          /jobs?id=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.

That page does not only keep experience, it keeps too academic qualifications, 
languages, desired contract, location, certification if they are enabled, ...

Maybe qualification is not the right word, but I think experience does not fit 
too. I think qualifications is better.

What about "resume" or something similar?



> >   https://gnuherds.org/Manage_Job_Offers.php
>
> How about "/jobs?owner=me"?

OK


> >   https://gnuherds.org/View_Job_Applications_State.php
>
> I suggest "/jobs?applied=yes".

OK


> >   https://gnuherds.org/Job_Offer.php?JobOfferId=XXX
> >                       /offer or /joboffer ???
>
> Is this different from View_Job_Offer.php?
Yes, this is only for edit job offer.

Here, I think we should use something like what you suggested below:
   "/jobs?action=edit&id=XXX"



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

This is to show all the candidates of a job offer, and be able to set her/his 
state to: "Received", "In Process", "Ruled out", "Finalist" or "Selected".

Maybe this?  "/jobs?action=manage&id=XXX"



> >   https://gnuherds.org/View_Qualifications.php?EntityId=XXX
> >                       /view_qualifications?EntityId=XXX
>
> How about just "/qualifications?id=XXX"?

What about "/resume?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=edit") and filtering (e.g., "?id=XXX" and "?applied=yes").

Cool!. We can follow improving it.

P.S.: I have been overloaded. The next month you will see as sometimes I will 
be unable to reply quickly.

Added task: https://savannah.nongnu.org/task/index.php?6819

Davi