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/
n6http://data.yelp.com/Business/id/
revhttp://purl.org/stuff/rev#
xsdhhttp://www.w3.org/2001/XMLSchema#
n7http://data.yelp.com/User/id/

Statements

Subject Item
n2:a_8t3irA5Xd1W4P5gCTb2Q
rdf:type
rev:Review
schema:dateCreated
2011-02-17T00:00:00
schema:itemReviewed
n6:pWuc0bDPg26Py0mBNyEQZw
n3:funnyReviews
0
rev:rating
1
n3:usefulReviews
13
rev:text
My family and I were looking for a good dentist close to home. Since this was a good location and nice office we thought this was going to be perfect for us. Unfortunately, things didn't end up as we had hoped/planned. Every (yes, EVERY) appointment we had made (at least 6 months in advance), we were called to change our appointment for another date because they overbooked or we showed up for our dentist appointment to find out that they "must have lost our appointment" (which we had already received an email confirmation). We understand if this happens once or twice, but when it happened half a dozen times we decided to never go back there for dental care. One time I received an email saying that I was due for a cleaning that week at a certain date/time. Since I book months in advance I figured this was the one I had booked so I showed up. As I was waiting in the front office I realized I had just been there 2 months ago for a cleaning. I went and talked to the man at the front desk and he said, "Oh yea, that's weird, I don't know why we booked you this month...well you can't get a cleaning today." This is just one instance of many. It may be a "pretty" office, but it is run poorly and we (and others) will never go back.
n3:coolReviews
0
rev:reviewer
n7:zi2zwTe0z_s37H3DxbvMlw