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
n7http://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#
n5http://data.yelp.com/User/id/

Statements

Subject Item
n2:NpaCDxJ97gpdnTqFmILTbQ
rdf:type
rev:Review
schema:dateCreated
2014-08-19T00:00:00
schema:itemReviewed
n6:00pYR20Rbt8c1r86UNlBJg
n7:funnyReviews
0
rev:rating
2
n7:usefulReviews
3
rev:text
I'm super let down by Tin Front. I'm going to give them a pass and revisit the next time I'm in Homewood, but my guess is my experience was "meh" for several reasons. 1. Odd time (4pm) 2. Lunch (vs. dinner) 3. Service issues Based on others' reviews, I was excited to grab an early dinner prior to a meeting in the area. After waiting for 10 minutes for someone to actually pay attention to me, I was met with one of the most awkward exchanges I've ever had. A man (couldn't tell if he was the owner, a server, a bartender, etc.) just randomly appeared and didn't really say anything. After I was able to confirm he was in fact associated with the restaurant, apparently we never did connect on exactly how to order food (i.e. sit down at a table with service, order at the bar, etc.). After almost walking out on the exchange, I finally placed an order for an arugula salad and coffee at the bar and grabbed a seat at a table. The saving grace that rescues Tin Front is that the food was decent. Nothing that blew me away, but definitely a solid offering. I wish that the dinner menu would have been available, because many of the options online did look quite appetizing. Either way, the experience stands as-is. Until I get a chance to revisit this joint, it'll sit as a 2-star in my book.
n7:coolReviews
0
rev:reviewer
n5:7aaA3Z0i7_XmjQWkamPlmQ