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/
revhttp://purl.org/stuff/rev#
n5http://data.yelp.com/Business/id/
xsdhhttp://www.w3.org/2001/XMLSchema#
n7http://data.yelp.com/User/id/

Statements

Subject Item
n2:UusU1ezAlY-e1J7KQrGdQA
rdf:type
rev:Review
schema:dateCreated
2018-06-02T00:00:00
schema:itemReviewed
n5:epQzqMPbNjh5t0Td3T6TJA
n3:funnyReviews
0
rev:rating
1
n3:usefulReviews
0
rev:text
BEWARE: Even if you accept the service deficiencies that you'll read about in the rest of the reviews here (and elsewhere), there's still the very realistic risk of you ending up with fraudulent charges on your credit card. In my case, a member (or ZipCar employee) lost/misplaced/stole the key to a car that I had days before, and ZipCar pinned it on me, among others, with absolutely no explanation. Calls to their customer service are often hung up on/put into a permanent hold. The explanation/justification they give is that in cases like this, they "investigate" the last few members who had the car to determine who is "most likely" to be responsible. In my case, I returned the car to the home location and ZipCar themselves confirmed that there were others in the car after me, and yet I was still being help responsible. They never resolved this matter, but continued to charge the monthly fee while my ZipCar account was frozen. Easily disputed this with the credit card company, but the spent hours upon hours on this. Don't bother; it's not worth it.
n3:coolReviews
0
rev:reviewer
n7:BkjMvrAAVs3XsQ6zSezuPg