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/
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:LyHPXf0Z2zzDn_AhxZLo_g
rdf:type
rev:Review
schema:dateCreated
2012-03-30T00:00:00
schema:itemReviewed
n7:2Bq5fySAwrNa8xotw2EJDQ
n5:funnyReviews
0
rev:rating
2
n5:usefulReviews
3
rev:text
My experience is a lot like Jason B. Our air conditioner wasn't working. We called the warranty folks who sent these guys over. The mechanic, Scott, was really nice. He set about doing his work and told me what would need fixing. I had to follow up several times after Scott's visit before learning what the next steps would be. This experience was similar to Jason's, with the whole "we're waiting on the part which is why we didn't get back to you." The only time they could schedule appointment number two was right in the middle of the work day - which was frustrating for me. I took off work. Scott came and fixed the ac. Again, he was very friendly. When he left, I noticed that the thermostat was not working. I called yesterday to let them know. The man on the phone was friendly and said Scott would be here between 7 and 9 this morning (again, having to take off from work). It's 9:15. Scott isn't here. I called the company and they explained that he had to take care of something else first. A call would have been nice. As you can tell by my short tone, I'm not very happy. If this was not covered by our warranty, I would have said goodbye to this company a while ago.
n5:coolReviews
1
rev:reviewer
n4:N_GCDLRq_EssIY-wStxOoQ