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/
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:Go1SP_b53eu5vshXpgbp8A
rdf:type
rev:Review
schema:dateCreated
2015-06-23T00:00:00
schema:itemReviewed
n6:ILq2TVP7mEJ1E-VoAt1_vw
n4:funnyReviews
1
rev:rating
3
n4:usefulReviews
3
rev:text
I used to be quite fond of this place, but I just had a not so awesome experience. I'm going to split the difference and go with three stars... but I'll likely only come back for my lunch needs, and never again for a juice fix, and I remain pretty unimpressed with their Saturday staff. Their vegan treats are delicious, and they do make their juices in house. However, they don't make juices to order, and sometimes later in the day the cups of green juices (what I'm usually after at this type of place), need some refreshing. My annoyance is surrounding their juice ingredients not being clearly listed (on the plastic cup options). I recently went for one of these bad boys and when I asked the girl at the counter what was in it, she said: "like so much, pretty much everything." What does that even mean? I asked her to clarify, she didn't/couldn't. I asked about the couple of things I can't have and am adverse to, and they weren't in there, she seemed to know what was *not* in the drink, so I went for it. It ended up being a very grainy and chunky juice, which I probably would have known beforehand, had she just taken the time to explain the ingredients. I rarely complain about service, but this instance really got my goat, especially since this kind of treat is pretty pricy.
n4:coolReviews
2
rev:reviewer
n7:Q9mA60HnY87C1TW5kjAZ6Q