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

Statements

Subject Item
n2:Lud5fkOJbFEa8Eewb4Z1OA
rdf:type
rev:Review
schema:dateCreated
2016-10-31T00:00:00
schema:itemReviewed
n7:i6FdasoJZdhqT1tJBGRScw
n3:funnyReviews
0
rev:rating
1
n3:usefulReviews
4
rev:text
It is unfortunate that my fiancé and I will not be booking our 2017 wedding at this venue. One star for the lack of professionalism and communication. We have been in contact with Anastacio since the end of June planning an October 28, 2017 wedding which although it was clear we could not go into contract until exactly 1 year to the day, our correspondences made us assume the probability of receiving at least our back up date was very high. I emailed Anastacio intermittently between July and October 28th to reaffirm our interest in the date. He would reply for us to wait until the 28th of October to check on the date. On October 29th I was informed that the date was taken by another bride. This was fine as I knew we were second on the wait list but I am dissapointed that I was then told that not only was our back up date taken, but so were ALL OTHER DATES IN 2017. He then suggested an entirely different venue to book at which I thought was beyond tacky (almost worse than the myriad of typos in his email). I am dissapointed I was not notified earlier of an event being booked on my back up date as I doubt it occured on the date I emailed him. I have been waiting 4 months to continue to plan my wedding and now I am back to square 1.
n3:coolReviews
1
rev:reviewer
n5:pILXiFdfDCoHp8cgNY8dtA