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/
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:E0q664gBLPopKtGmLp0QYQ
rdf:type
rev:Review
schema:dateCreated
2016-08-12T00:00:00
schema:itemReviewed
n6:d-2g8JWtXuYsOqZtbFuZtw
n5:funnyReviews
0
rev:rating
3
n5:usefulReviews
2
rev:text
Pool tile cleaning was well done, tile looks great. The problem was with the delays in the tile repair work requested. We drained our pool on Monday in preparation for the tile cleaning and repair first thing Tuesday morning. Tile cleaning was done by 10 AM, no problem. Unfortunately, the tile repair was a no-show. We called BF and they seemed a bit disappointed as well because they had not heard from the repair person either. There was a bit of weather in the area so perhaps that's why he never showed. No-show on Wednesday again, we called BF and were told he would be here between 3:00 and 6:00 PM, or if he was tied up, would be here Thursday between 6:30 and 7:00 AM. Nothing Wednesday evening, 7:00 AM rolls around on Thursday, nothing, finally he shows up at 8:30 on Thursday morning. The repair was done well and quickly, I just wish it wouldn't have taken two additional days to get it completed. Additionally, I was concerned that our pool was drained for the better part of four days and the Pebble Tec was exposed directly to the sun. Fortunately, we had a break from the triple digit weather. Communication was very good throughout the process. I would use BF again for tile cleaning, but not so sure about repair.
n5:coolReviews
0
rev:reviewer
n7:Hblexn1Jt1Fh1USliLh1yA