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:zV6lRly0f9mZZ_e1hsLTfA
rdf:type
rev:Review
schema:dateCreated
2016-10-17T00:00:00
schema:itemReviewed
n7:eQCYur0033RkZdh5VjbF8A
n5:funnyReviews
1
rev:rating
2
n5:usefulReviews
1
rev:text
Disappointing, and not that good. Went for a Sunday brunch, the place was about 1/2 full. I had the Huevos Rancheros, which were not poor but mostly tasteless. Hard to imagine how the kitchen pulled that off with those ingredients. My last meal at O&B was overly salty, and I had to complain about that, so maybe the kitchen hid the seasonings when they saw me coming. Not enough food to satisfy, unless they think "brunch" is a meal in between a full breakfast and lunch, and not a substitute for both. My companion had the breakfast plate but asked for no pork, and was served both bacon and sausage. Pork is really something that a restaurant should be aware of. Our server disappeared after taking our order, when the bill came there was another one. So no drink refills for us. How a restaurant manages a shift change at 1:00 pm is bewildering. Coffee was good but cold, so not. Washrooms smelled. This was my second disappointing visit to O&B and I regretted my decision both times. In a world of foodies and food TV and interesting dining everywhere, it's hard to believe that a marquis name can get away with delivering an experience as mediocre as the one I just paid for. I will be avoiding O&B from now on.
n5:coolReviews
0
rev:reviewer
n4:ZGY-dDfljWJap6WNgptWuQ