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:uyUDCotySrzLuHPefzaGTg
rdf:type
rev:Review
schema:dateCreated
2014-06-21T00:00:00
schema:itemReviewed
n6:O_UC_izJXcAmkm6HlEyGSA
n3:funnyReviews
0
rev:rating
2
n3:usefulReviews
2
rev:text
I've been a Playa Cabana fan for a few years now: excellent food, fun ambiance, what more could you ask for? Well, service, it turns out. The last several times I've been to Playa Cabana, my party and I have been seated within' reasonable time, only to have to wait over an hour for our entreƩ-- an hour. If this happened once, or even twice, I'd let it go, assuming that the kitchen was understaffed or some other issue, but three times is just one too many. Additionally, even if there were some issue with staff, a quick word of warning from the server might give us some options: do we want to order another round of apps while we wait? Are we even okay with such a long wait? But no, in none of these instances were we ever informed that there would be an hour wait after ordering. As a patron, it was frustrating, and as a host to out of town visitors, it was outright embarrassing. To the management of Playa Cabana: guests aren't unreasonable. A little communication about a situation can go a long way. As for myself, I won't be coming back or recommending the restaurant until some of these services issues are addressed.
n3:coolReviews
0
rev:reviewer
n7:fYgBBpBvQiUyzULqQsphYQ