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
n4http://www.openvoc.eu/poi#
schemahttp://schema.org/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.yelp.com/Review/id/
revhttp://purl.org/stuff/rev#
n5http://data.yelp.com/Business/id/
xsdhhttp://www.w3.org/2001/XMLSchema#
n7http://data.yelp.com/User/id/

Statements

Subject Item
n2:peo7oP-iHmTnqXW8lOIDuw
rdf:type
rev:Review
schema:dateCreated
2016-08-05T00:00:00
schema:itemReviewed
n5:5qyVOOsTxMdEByXVkH6LQg
n4:funnyReviews
1
rev:rating
2
n4:usefulReviews
2
rev:text
I'm disappointed every time I come here. I come here simply because it's the closest one. Maybe I shouldn't. There's one a few minutes away that might be better. This particular time I avoided the drive through (it ALWAYS takes longer than it should but that's another story), and went inside. There was one girl ahead of me and a guy named "Al" behind me. I only know that because everyone greeted him by name. Even came out with his drink. I ordered and Al paid. The girl got her drink and then both patrons left. I waited another 5 minutes before someone asked me if I was waiting for food. I said no. Then the other barista said he's probably waiting for this and handed me my drink. I confirmed it was right. It was. I was just so confused how a guy got his drink before me, how the barista was making far more complicated orders before mine (I know they were drive-thru but there were two baristas making drinks) and I still managed to wait so long for a cold brew (iced coffee you just pour into a cup!). I used to work for Starbucks years ago and this wouldn't have been okay at my store. I'm sadly disappointed in the standard I've seen at Starbucks lately.
n4:coolReviews
0
rev:reviewer
n7:fiaClUmPLo5hHDCh5t979w