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/
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:OqNuwL7oTkyzYjOnL0uUjQ
rdf:type
rev:Review
schema:dateCreated
2012-12-08T00:00:00
schema:itemReviewed
n6:RQxLNvAra_MUUPHdhukilA
n5:funnyReviews
1
rev:rating
3
n5:usefulReviews
4
rev:text
So here's the thing: after 4 times here the service has been consistently friendly but incompetent. For example, today I got sat in a nearly empty restaurant, and the host forgot to bring a menu. She said she'd bring one right back, and then forgot (I watched her stand at the host stand, bored). Took 5 minutes to get one from waiter. This is the kind of thing you'd forgive as a fluke, but you watch and see table-waiting basics being flubbed all over the place. Last time, I watched *three* different customers standing up and approach a waiter stand asking to find their waiter. My service was slow, and didn't anticipate common needs (like a coffee refill at breakfast). My food came out partially cold and partially hot, which is either a kitchen timing issue or a tardy waiter who left food sitting in the window too long. Seeing as it doesn't seem to be one bad server, I'd guess this the result of poor training--which is usually a management issue. If you can survive the service, the hip/classy atmosphere has rich dark wood, orange lighting, and attractive window bays looking at Memorial Stadium on the south tip of campus. The menu items I've had have been either decent or great. Worth a try, I suppose, but bring patience.
n5:coolReviews
1
rev:reviewer
n7:zuKR4B3CdrnA4HpqFvaVJQ