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:NRQudSuwDhx6XKdz-dupdw
rdf:type
rev:Review
schema:dateCreated
2010-05-29T00:00:00
schema:itemReviewed
n6:OtGSQQzV7uF8XPAsNIh7Bw
n3:funnyReviews
0
rev:rating
2
n3:usefulReviews
0
rev:text
Allow me to start out by saying I never thought I would be the type of person to write an email regarding a dining experience (good or bad). Having said that, the only positive thing I can say about our evening at your restaurant was that the valet guy was very pleasant and friendly. It was a special evening for my girlfriends birthday (I called ahead and pre-ordered flowers for the table). Our drinks took way longer than they should have, the main courses and side dishes were average, the time between clearing our plates and dropping off dessert menu's was at least 15 minutes, and the birthday dessert was far from impressive. I would most certainly have informed a manager but didn't have the opportunity since there was no table check during our meal (isn't this standard at fine dining?). Not to mention I would love to inform you of our incredibly boring server's name but I have no idea what it was since he never introduced himself! I hate to sound so crude but with that beautiful location and relatively pricey per person check average, we expected a little more. Perhaps a little less time filming shows for the Food Network and a little more time focusing on the little things that create a memorable experience is in order? Just a thought.
n3:coolReviews
0
rev:reviewer
n7:iuz4lXjzwaxuFWaLqUl6gA