V0 Specifications

Table of Contents Features User Registration User Identification Consult and Change User informations Consult Members list Consult Members profiles Private Messages Event Creation Event Consultation Event Location (Geolocation) Data encoding

Features

User Registration

• Username: Each member has to have an Username. Several members can have the same username. Only letters and numbers (< 64 characters)
• Email: Each member has his own email which is unique to this specific user/member. (< 64 characters)
• Password: must be at least 2 characters long. Can only contain letters and numbers.

User Identification

• User Email: Identification is done by an unique field which is the email.
• User password: Must match the registered password

Consult and Change User informations

• Username (see User Registration)
• Email (see User Registration)
• First name: must only be letters (< 64 characters)
• Last name: must only be letters (< 64 characters)
• Birthday date: ('mm/dd/yyyy hh:mm' or 'yyyy-mm-dd hh:mm')
• Nationality: List of all existing nationalities
• Gender: Male or Female
• Upload or link to a profile picture -> V1

Consult Members list

Each Member can have access to the list member. For each member, display a sum up:

• Profile picture Icon -> v1
• User name
• Age
• Number of current events
• Last connection/Geolocation -> v1

(Favorite events)

Consult Members profiles

• Profile picture -> v1
• User name
• Age
• Number of events posted
• Current events planned
• Last connection / Geolocation -> v1

Private Messages

• Members must be able to communicate between each other -> v1 or later

Event Creation

• Event type: must match the event types defined in the database (Activities, Visits, Journeys and Parties for now) -> for v0, only 1 ou 2 types
• Event name: only letters allowed and must be longer than 3 characters
• Event location: (see Event Geolocation)
• Event Check in date: 'mm/dd/yyyy hh:mm' or 'yyyy-mm-dd hh:mm'
• Event Check out date: 'mm/dd/yyyy hh:mm' or 'yyyy-mm-dd hh:mm' or 'unknown'
• Languages spoken at the event: list of all languages spoken and recognized as official languages in the world
• Maximal number of participants: just a number, no restrictions
• Description: use html allows to restrict message length to a number of character. Set as 4000 max for now.

(Add someone as an one of the event holder) -> html in v1

Event Consultation

• Event type
• Event name
• Event location: (see Event Geolocation)
• Event Check in date
• Event Check out date
• Languages spoken at the event
• Maximal number of participants
• Description
• Holders
• (Image according to the location?)

Event Location (Geolocation)

Except for adress, latitude/longitude, country, all other -> v1

Each Event has to be geolocated before being registered in the database. We cannot save an event with an unknown geolocated point/address. A geocolated point contains the following informations:

• Latitude (Mandatory)
• Longitude (Mandatory)
• Bounds
  • South
  • West
  • North
  • East
• Street Number (Mandatory)
• Street Name (Mandatory)
• City District (Mandatory according to countries)
• City (Mandatory)
• Zipcode (Mandatory)
• County
• County Code
• Region
• Region Code
• Country (Mandatory)
• CountryCode (Mandatory)
• Timezone (Mandatory)

Data encoding

All datas (strings) have to be encoded in UTF8 before to be saved in the database