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
n6http://www.openvoc.eu/poi#
schemahttp://schema.org/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.yelp.com/Review/id/
n5http://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:PJQNgzHniYKVGN2c80rJOw
rdf:type
rev:Review
schema:dateCreated
2010-10-23T00:00:00
schema:itemReviewed
n5:8IcbdMa1wC2hOxwHBO9a1g
n6:funnyReviews
1
rev:rating
1
n6:usefulReviews
3
rev:text
Contacted Darrel's locating to locate a water leak that was found on a commercial property in Tempe that I handle. Darrel arrived removed his equipment and said he located the leak under the concrete slab where the driveway met the garage. I also had him mark the water supply line from the city water service to the house so we could identify where we had to make access to the leak and what concrete we would have to remove. We demo'd the driveway to get to the leak that was identified by Darrel. Well the leak wasn't there and the supply lines weren't even close to the lines he marked. We found the leak on our own and it was BEFORE it entered under the driveway. $1400 worth of concrete work and a days extra digging because this man rushed through the job a missed the leak by over 10 feet. I called him to ask what his policy is regarding such a major error and he replies, "Well we can come out and try again other than that its just a missed detection and it happens". Excuse me Darrel we already found the leak on our own AFTER digging up a driveway where you said it was. I don't need that kind of help. A repair that could have cost a few hundred to fix turned into a few thousand thank to Darrel's leak detection or in this case, Darrel's I don't have a clue
n6:coolReviews
1
rev:reviewer
n7:QkHp5bEoxyn-GbI8OsU84A