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
n3http://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#
n5http://data.yelp.com/Business/id/
xsdhhttp://www.w3.org/2001/XMLSchema#
n7http://data.yelp.com/User/id/

Statements

Subject Item
n2:QK4_fF9qeAnm6TwCMTre7g
rdf:type
rev:Review
schema:dateCreated
2018-04-02T00:00:00
schema:itemReviewed
n5:0s9C979YGRjoUQAsaDB3RQ
n3:funnyReviews
0
rev:rating
1
n3:usefulReviews
0
rev:text
I'm a little frustrated with my experience today. I called and made an appointment last week for a tire change and an inspection. I'm preparing to travel for a while and am rushing to get all my loose ends tied up before I go. I told them that I was going to come in on my lunch break and was told it shouldn't take more than an hour, which was perfect. I arrived today for my appointment and was told that they had a technician call out and that they wouldn't be able to service my car. I explained to the guy that I'm in a time crunch and need to get it done before Thursday. He said that if I could leave my car with them for the rest of the day they MIGHT be able to do it, but he sounded very doubtful. Since leaving my car would require me to take an Uber back to work, it didn't seem worth the gamble. He didn't even offer to try and reschedule. I can completely empathize with how some things can't be anticipated (like having a team member out sick), but it would have been nice if they had called me in advance to let me know that they couldn't keep my appointment, as opposed to turning me away when I arrived. I really could have used that time to get it done elsewhere or to check something else off my to-do list before I go.
n3:coolReviews
0
rev:reviewer
n7:UEgrI8VqNH33vVdWwqvaMA