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:L9BIL75CtHzQq51BNos4BQ
rdf:type
rev:Review
schema:dateCreated
2011-10-24T00:00:00
schema:itemReviewed
n6:xpHrwe2X-X9K81TEz_W9Cw
n3:funnyReviews
0
rev:rating
3
n3:usefulReviews
4
rev:text
Agree with most posters about the setup - left much to be desired. I was smart and arrived BEFORE 4:00 P.M. so I could jump in early for some short and FAST lines. My 15-yr-old son was with me, and he's a fairly picky eater, which was one reason I brought him - so he could see that there are other foods he might like if he TRIED them. I got a lot of food between 4:00 and 4:30, when the lines were short. I probably got to try 10 trucks before we left at 5:07. We went back to some trucks more than twice or three times when we found something we liked. My advice for future events: 1. Help the trucks deliver the samples FASTER. Not sure how - maybe get them an extra staff member? But the samples on some trucks were coming SLOWLY, so that needs to improve. 2. Better location, maybe not on dirt, and maybe a little larger. Once the lines got up to 20-30 people, the going was CRAMPED and it was taking a long time to get your samples. 3. Maybe a lower price for tickets? Seemed kinda steep for the amount of food each person received. All in all, I enjoyed the FOOD, but the rest of the logistics, not so much.
n3:coolReviews
1
rev:reviewer
n7:jfGevhcYLxY13Fa3drpzoA