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
n5http://www.openvoc.eu/poi#
schemahttp://schema.org/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.yelp.com/Review/id/
revhttp://purl.org/stuff/rev#
n4http://data.yelp.com/Business/id/
xsdhhttp://www.w3.org/2001/XMLSchema#
n7http://data.yelp.com/User/id/

Statements

Subject Item
n2:f0Jt7Nwwc2yKWKwrqAzuMg
rdf:type
rev:Review
schema:dateCreated
2018-02-20T00:00:00
schema:itemReviewed
n4:4wlbwuT3zQJmtDH24WrXvQ
n5:funnyReviews
0
rev:rating
1
n5:usefulReviews
0
rev:text
We have had a couple of hiccups with this groomer now. Price quoting was the first. Both my husband and myself clearly heard them quote a recut price after the first cut. I paid them after the 2nd cut and she came back in stating I had shorted the payment. We didn't like it but anybody can make one mistake, right? I am severely disabled (they are aware) and don't always check my email right awY. I had sent an email about scheduling an appointment. They emailed back same day with a price and stated they had availability today between 12:00 and 1:00. I didn't check my email until Sunday due to pain issues. I emailed back on Sunday letting them know I'd take it and they JUST emailed me back today letting me know that appointment is gone and they can't come today. Well that would've been nice to know before I had my husband leave work early to pull out cash for today's appointment. They should've emailed back, or called, before today. The email is stamped 10:35 am. Thus is not acceptable for a noon appointment. Save yourself the time and headache. This team clearly has a communication problem.
n5:coolReviews
0
rev:reviewer
n7:WCLKFHgH8wvAxg1_21gMvw