Unele persoane au dificultăţi în alegerea ţinutei potrivite pentru un anumit tip de eveniment (interviu, dineu oficial, spectacol etc.). Să se dezvolte o aplicaţie Web care permite alegerea pieselor de îmbrăcăminte corespunzătoare pe baza garderobei existente – diversele informaţii de interes pot fi preluate de la DBpedia sau Freebase. Se vor oferi sugestii conform tendinţelor modei, sezonului, cromaticii dorite şi/sau stilului vestimentar adoptat de persoana respectivă. De asemenea, se vor pune la dispoziţie informaţii utile referitoare la achiziţionarea unor produse de interes, în funcţie de localizarea geografică a utilizatorului.

1. SEC
Semantic Clothing

2. Authors
● Negru Ionut Valentin
● Nistor Andrei
● Alexandru Andrei

3. Summary
1. Use case
2. Application’s architecture
3. REST API description
4. Data modeling
5. Implementation
6. Optimization
Project link: wad.nistorandrei.com

4. 1.Use case
The application will offer the following use cases:
1. Find cloths based on well established filters
2. Automatically detect and apply filters to return only
results of interest to the user
3. Offer suggestions based on the searches made by
the user

5. 2.Architecture

6. 2.Architecture
The sequence diagram of an User
accessing the REST API.
The authentication is required to
create responses as specific as
possible, depending on the data
offered by the user.

7. 3.Rest API
Persone Methods:
GET /person
GET /person/:ID
POST /person
PUT /person/:ID/edit
DELETE /person/:ID
Wardrobe Methods:
GET /person/:ID/wardrobe
GET /person/:ID/wardrobe/:WARDROBE_ID
POST /person/:ID/wardrobe
PUT /person/:ID/wardrobe/:WARDROBE_ID/edit
DELETE /person/:ID/wardrobe/:WARDROBE_ID
Examples:
GET http://wad.nistorandrei.com/api/person/gender/male
GET
http://wad.nistorandrei.com/api/person/10/wardrobe/color/bla
ck|red/season/winter/gender/male
More info @ http://wad.nistorandrei.com/doc_api/

8. 4.Data modeling
All data retrieved from Freebase and/or
DBpedia will be processed as JSON.
The response given by the REST API will be in
JSON format.
Libraries for modelling data into RDFa data will
be used on the client side.

9. 5.Implementation
The application will have two major components: server &
client
The client will take care of the user’s profile, UI and
response parsing.
The server will take care of the big queries at Freebase &
DBpedia, of the response processing and modelling. On
the server side the actual filter will also be made,before &
after the queries.

10. 5.Implementation
For the implementation process we will use:
❖ server side: Laravel
❖ client side: Blade, JavaScript/jQuery, HMTL
❖ FreeBase with MQL
❖ DBPedia with SPARQL
❖ Custom Crawler to save products in
database

11. 6.Optimizations
❖ Secure REST API
❖ Optimize big queries (chunks of data)
❖ Optimize data modeling (chunks of data)
❖ Cache with optimal invalidate methods
❖ Server side suggestions (our DB wihtout
query)

12. Thank you
Any suggestions ??