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:fMJyT29E2NhJK1j8JK4VdA
rdf:type
rev:Review
schema:dateCreated
2015-03-15T00:00:00
schema:itemReviewed
n7:bzbNGyrTwWHAgg1CqkSgeg
n5:funnyReviews
0
rev:rating
2
n5:usefulReviews
0
rev:text
The below review was written by my husband.... Went on Sunday. Supposedly, you can't make reservations for Sunday, but I heard people doing "call aheads" ... which is the same as a reservation in my book! Put name on list for 15-20 minute wait. Waited more that 20 minutes. Went inside and asked for update. Hostess said she texted our phone twice with no response and then deleted our spot. We received absolutely NO texts. This happened to 2-3 other people that I personally witnessed. Other groups of more people arrived ahead of us, ate and left before us (on a day with no reservations). The chicken apple sausage used to be two links (I think) and now it's one link cut lengthwise. The crab cakes benedict were ok and my wife's pancakes were ok, but they didn't say that the cakes came with powdered sugar by default which is something she doesn't like. So, the wait and the "ok" food are enough of a reason to not go back for Sunday breakfast for quite a while. We loved our server and the hostess seated us immediately after I asked for an update. So, I'd have to say that the service was decent, but was the overall experience compelling enough to warrant a return visit (any time soon)? No.
n5:coolReviews
0
rev:reviewer
n4:cVitpbprQZ1zihsZk8fLKg