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:Put9IYiGOBLSx0sB0ZzgbA
rdf:type
rev:Review
schema:dateCreated
2014-01-12T00:00:00
schema:itemReviewed
n7:1HfkEkNhI6XJXkgrCTBKpw
n5:funnyReviews
0
rev:rating
3
n5:usefulReviews
1
rev:text
Such mixed feelings!!!!! If I am simply reviewing the food that I've had thus far, I'm giving it a solid 4 stars, maybe even 4 and a half. They present a creative menu, definitely far and above normal bar food, and most importantly, they execute it well. Kudos all around for that. I'm okay with the space, though I think it does seem a bit confused. What is it? A gastropub? A great foodie destination? A frat boy sports bar? Who knows... This "identity problem" seems to carry over to service, unfortunately. I've experienced the perfect balance of friendly, knowledgeable and professional along with the dismal bar server who looked hungover, acted hungover AND chatted about her hangover with unengaged employees, hanging around the bar, lounging on a banquette, oblivious to the presence of customers. Coupled with a group of old-enough-to-know-better guys at the bar who acted like they just discovered the F-word (and couldn't say it often or loud enough...) definitely detracted from what would have been a perfect brunch. For this reviewer, it seems easy enough to back up this great food with great service, but thus far it just isn't happening. Management needs to be as involved with service as they are with culinary creativity & excellence. Casual doesn't equal lazy.
n5:coolReviews
1
rev:reviewer
n4:AMEEmwStgP_OBGwAL-tO4A