This HTML5 document contains 9 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
n6http://www.openvoc.eu/poi#
schemahttp://schema.org/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.yelp.com/Review/id/
n7http://data.yelp.com/Business/id/
revhttp://purl.org/stuff/rev#
xsdhhttp://www.w3.org/2001/XMLSchema#
n4http://data.yelp.com/User/id/

Statements

Subject Item
n2:RoSz-2q4cF89nLIW88iGVA
rdf:type
rev:Review
schema:dateCreated
2012-05-29T00:00:00
schema:itemReviewed
n7:xpocpPlEWaQygGMLSvjelQ
n6:funnyReviews
1
rev:rating
3
n6:usefulReviews
14
rev:text
It's.... fine. I went twice for hair cuts last year. The place is really bustling and both times I had to wait in a long line to check in, along with people who were checking out/paying. They should consider separate lines if they haven't yet. The lobby is full of uber tacky cheap handbags and accessories. It's kind of a turn off. The first time I got a cut it was okay, but I was not wowed or anything. So when I called back a few months later for another cut, I asked for a different stylist. Well the girl on the phone didn't seem to like that and went into a thing about how I should give the other one a second chance to redeem or whatever. I protested but she insisted that I would be happy and the stylist would listen to my concerns about the previous cut. So I caved. I needed a cut that night for an event the next day and didn't feel like debating on the phone. This time I brought a picture of the kinds of layers I wanted, but still ended up with just one short layer over a long layer. So pretty flat and boring. I dunno, I've had other stylists just know how to work it without much input from me. So neither of the cuts were awful, just nothing special. I have since moved on to a different salon.
n6:coolReviews
1
rev:reviewer
n4:JV4mCFFKgf_AurjiAXqq7w