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

Statements

Subject Item
n2:dXstxWql1i0NgaY-M4dwuA
rdf:type
rev:Review
schema:dateCreated
2018-03-03T00:00:00
schema:itemReviewed
n4:DK6RvPJiCmCBXgeJEmjIfQ
n6:funnyReviews
0
rev:rating
1
n6:usefulReviews
0
rev:text
The funeral director who we met with was very nice and efficient. We expressed our wishes and he took the time to ensure that everything would be in order for our Thursday family goodbye. When we were brought to the room where my father lay, we were mortified that he was not presented as we had discussed and agreed upon. We were told by the young woman staff member that they had to check to make sure the cremation container we had requested was in stock (Seriously??) as they had to be preordered. We were asked to wait in the outer area while the staff made the changes and then we were allowed to go back into the room, when the horrendous error was rectified. The staff all apologized, as did the owner, Evan J. Strong however, at a time such as this, we cannot ever go back for a "do over" and it has left a permanent scar on our family. No amount of apologies can make this horrendous error right. I feel that my father's memory has been dishonoured and I am deeply regretful that this was our choice for him to be cared for. The timeline for making the arrangements was sudden and short and my family certainly didn't need the added stress of someone's senseless oversight and errors to permanently mar my fathers memory.
n6:coolReviews
0
rev:reviewer
n7:R2S1FjqRwh8KBPngxUkGtQ