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
n7http://www.openvoc.eu/poi#
schemahttp://schema.org/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.yelp.com/Review/id/
n6http://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:Zd-aOJ9XiflqgZybJxJo1A
rdf:type
rev:Review
schema:dateCreated
2016-10-02T00:00:00
schema:itemReviewed
n6:kOZohaAywZ8GFF6YjOyBVQ
n7:funnyReviews
1
rev:rating
1
n7:usefulReviews
1
rev:text
Going to agree with Thuriya here. When I went in I had 3 requests: 1.) Do not change the length of the top hair. 2.) Shorten the sides to a 4. 3.) Thin the top. In the process of cutting the sides, my hair went from down to my chin to eye level. As justification the goal was to make it so that it would be even. With the original length it would have been possible to just slick the hair back until the sides grew back in, but the top length was cut by 3 inches. I had spent the first half of the year growing it to this length, because most hair stylists tend to cut it short. In terms of how to avoid the scenario it would have been easy to just clip the top hair out of the way so that you can trim the sides with the hair clipper, not move the hair clipper up the side of the head with the top hair still hanging there. Oh and not to mention the lack of privacy. I need to give my phone number for the records so I can get a hair cut? Not true. For sake of ease? Hardly. I refused 3 times, but each time they kept pestering me for it.
n7:coolReviews
1
rev:reviewer
n4:vmZU2qbPQMwB6tWi73tM4A