Nomenclature cleanup

[Anonymous]

In both the documentation and the plugin itself, there are some confusions with terminology. Namely, the same thing is referred to with different names. I have run across a few but can only remember one for now. I will reply to this thread with more examples as I find them.

Here is the main one that caused me a lot of confusion at the beginning, and still does sometimes:

Booking Form / RSVP Template / Registration Form

The template should have the same name as the form it is used in. “Registration” is a very bad name for this form. Booking or RSVP are both fine, but you should choose only one name that appears everywhere (at least in the admin and docs).

[Franky]

Booking form and Registration form are the same.
RSVP template is something else: it is the template used to build the form. It stems from the fact that in the past there were no templates …
I’ll go around and take a look at nomenclature later on, but this is low priority for me 🙂 I’m open to all changes being submitted though.

[Anonymous]

Unfortunately my PHP skills might not be up to scratch here, but I see no reason why the template should have a different name than the form. One should be called the RSVP (or booking) form, the other the RSVP/booking template.

“Registration” is a term always associated with creating user accounts, never with signing up for events, so that was a poor choice from the start.

[Anonymous]

Confirming that this usage of “registration” (for an event) is very nonstandard English usage for the web and in general! It continues to be confusing for me even after 3 years using EME.

[Franky]

Feel free to suggest other wording 🙂

[Franky]

The next version will prefer “Booking” over anything else. I searched the net, and reservation has multiple meanings, while 1 of those is a synonym of a booking. Registration is also possible but is most of the time not used to reserve places.
So booking it will be 🙂

[Author]

Posts