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
n6http://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:Ml3x56hAHfeJCYE3APQnEw
rdf:type
rev:Review
schema:dateCreated
2015-08-11T00:00:00
schema:itemReviewed
n7:Wf7AV7JbR52qABil0bU8NA
n6:funnyReviews
0
rev:rating
1
n6:usefulReviews
3
rev:text
Expected to sit outside on the deck for a Friday night early dinner. They don't take reservations and the rather small outdoor seating is completely taken by happy hour guests who take up prime seating for hours with one drink. The beautiful view is inhibited by the poor window design with steel framing right at eye level for all the couples we were with. The acoustics were SO LOUD we were screaming the entire time and had headaches when we left. Just a little fabric on the ceilings and walls would take care of that! The service wasn't great, but the servers were running up and down stairs the entire time. When I asked for plates after she brought our appetizers I was told, "I'll see if I can find some" and she never returned with any. We were forced to eat with plastic utensils,,,,,,really? The food wasn't spectacular with the exception of the cheese curds. I was extremely disappointed to learn that the fried oyster po'boys they had on their website menu were no longer an option because "oh that menu is really old" and the waitress looked at me like I was the idiot (like when I asked for appetizer plates). Shouldn't your website menu be up-to-date? So much potential, so much disappointment. Our party agreed never to go back.
n6:coolReviews
1
rev:reviewer
n4:jn2j7eTGXLm6WwkaMQuZ_A