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:xgM4co0Wl0lMS0PJWyGnBQ
rdf:type
rev:Review
schema:dateCreated
2015-09-21T00:00:00
schema:itemReviewed
n6:0pMsVlUu_MbFqmvbA8F79Q
n4:funnyReviews
0
rev:rating
1
n4:usefulReviews
1
rev:text
If they weren't at a convenient location by ASU I swear... This one is not on the ball. The sandwiches were correct(ish) and timely but the staff left me perplexed. I wasn't asked at the beginning or end if I wanted any added toppings, which I thought was standard practice but whatever. Then when I asked for toppings I was looked at like I was weird... Excuse meee! Tasted good but the "Dank" is always sloppy, maybe people like but I don't, the bread is not crisp, soggy somehow, with sauce that spills out when picking it up and that makes the pepperoni slide out with the cheese... But this that the offense deserving of one star? No, but their communication is. I got a PRIVATE message from that manager/owner asking for my PHONE number to figure out what went wrong when my review is pretty black and white spelled out. It's not my fault or my job to talk about what the staff did wrong. Whatever needs to be said can be in an email or message. If I was just believed and spoken with decently I wouldn't be so disgruntled. I still drive 30min+ to visit the mcc one so the ingredients aren't the issue.
n4:coolReviews
0
rev:reviewer
n7:xTHoZ5p6P0SGr3Hh7PXQ_Q