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
n3http://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:n4I5_MCU9XIZk4p-oLN2Fg
rdf:type
rev:Review
schema:dateCreated
2009-02-25T00:00:00
schema:itemReviewed
n6:atNpoWy_XrhT9EUIEP6azg
n3:funnyReviews
1
rev:rating
2
n3:usefulReviews
5
rev:text
I was part of J-Man's brunch party last Sunday. Having had such a great experience at Metro the first time around, I was also really disappointed by the service (or lack thereof) we experienced. The food my husband and I ordered was actually very good (he had the burger with gruyere and I had the quiche as well as the vanilla-scented yogurt) but the service was just bad. Given the fact that the restaurant wasn't nearly as full as I've seen places at brunch and the fact that we weren't unusually demanding or confusing, I think that the bad service was unacceptable. Rather than sitting back and enjoying our friend's birthday brunch, we ended up literally spending half of our time reminding the server of things we needed but never got. When we eventually complained to the manager, she did comp a bottle of champagne but the service didn't improve after that. I really did enjoy the food I tried and thought the specialty drinks (try the French 75) were well-made but they all weren't good enough to compensate for the service. It seems like the bad service is a common complaint among Yelpers so I would hope the management/owners would take that into consideration and do something to make it better.
n3:coolReviews
3
rev:reviewer
n7:gru76BjkRY6UQVcw_yAxiQ