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
n5http://www.openvoc.eu/poi#
schemahttp://schema.org/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.yelp.com/Review/id/
n7http://data.yelp.com/Business/id/
revhttp://purl.org/stuff/rev#
xsdhhttp://www.w3.org/2001/XMLSchema#
n4http://data.yelp.com/User/id/

Statements

Subject Item
n2:TJjqsHXAZTJALtaez4YvAA
rdf:type
rev:Review
schema:dateCreated
2016-07-18T00:00:00
schema:itemReviewed
n7:FdkvHQ0VuFaxLsPGKz1_9A
n5:funnyReviews
0
rev:rating
3
n5:usefulReviews
0
rev:text
Pretty decent bike shop in the north end of the city. I ordered a lock from them that they didn't have in stock. The guy told me it would be in mid week the following week and they'd call me when it arrived. A week passed and no call. I finally went in the following week and the guy in the store told me that the lock had been back ordered. Then another guy told me it was on the shipping list but it didn't arrive. This normally isn't a huge deal; these things happen and I understand that but I had pre-paid for the lock (something I don't do generally for this exact reason) AND I had a trip planned for that weekend and needed the lock for that. Now I had to shell out MORE money to buy another lock. The manager was really good about the situation; he offered me 20% off the lock when it came in and when I explained the situation, he instead refunded my money right away so I could purchase the lock somewhere else. My main complaint was the fact that nobody called me to inform me of the situation and if I hadn't gone in, I never would have found out and been stuck on my weekend trip.
n5:coolReviews
0
rev:reviewer
n4:rvQ-F-6VDx9rugc92GEkfw