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:Du7naw0Z7YVNG5yjp5Sb3w
rdf:type
rev:Review
schema:dateCreated
2013-09-24T00:00:00
schema:itemReviewed
n6:BUcyHikUyo4U12-3RvDKlg
n4:funnyReviews
0
rev:rating
2
n4:usefulReviews
4
rev:text
A restaurant chain is only as good as it's weakest link. I've eaten Paradise Bakery foods before, including OK sandwiches, salads, cookies and so on. But my visit to this location was for one thing: a bagel. I love bagels, specifically everything bagels. So I ordered one toasted with roasted veggie cream cheese to go. It only took a minute for my order to be ready and I immediately took it out to my car for the drive home. Imagine my surprise when I found out (traveling down the interstate) that the bagel was 1) barely toasted 2) not warm and 3) the cream cheese was in a container for me to spread on myself. Of course, being a safe driver, I pull over to a parking lot to put together the bagel that, ordering to go, I thought would be ready-to-eat. The veggie cream cheese had crunchy veggies in it (not as roasted as I would assume), the bagel didn't have much flavor, I had to assemble it myself, and it was cold. Remind me why I didn't just go to a grocery store and purchase a bagel and cream cheese for about 1/4 the price? Suggestion: if it's ordered to-go, it should be ready-to-eat. Bagel rant end.
n4:coolReviews
1
rev:reviewer
n7:InLqIX5bb2M7H724adkYVg