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/
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:EXBcDhUuR0O9md6Oc3ujiw
rdf:type
rev:Review
schema:dateCreated
2015-11-16T00:00:00
schema:itemReviewed
n6:q9xum44SDEy3IMHV8Jf0KQ
n3:funnyReviews
1
rev:rating
5
n3:usefulReviews
2
rev:text
My boyfriend was the best man at a wedding in Phoenix this weekend, but we currently live on the East Coast. As excited as he was to be a part of the ceremony, he worried about how he would coordinate his tux from so far away. Thanks to Mr. Formal, everything went perfectly! To start, all the tuxes looked great and were reasonably priced. It's their customer service that really shines. Per their instructions, my boyfriend brought his measurements in for the fitting. Just from looking at the paper, DJ could tell that our local seamstress had done them wrong. Instead of it being a disaster, DJ got my boyfriend a tux that fit. He offered helpful suggestions all afternoon until we found the pieces that suited him perfectly. After all that, we then figured out that the groomsmen had accidentally picked up bow-ties instead of regular ties. DJ to the rescue! He got us the ties we needed the day before (in the correct color and pattern) and allowed us to bring all the ties back when we returned the suits. There are so many things that can go wrong in a wedding, but Mr. Formal helped this aspect go off without a hitch. I'm grateful to them and their expertise!
n3:coolReviews
1
rev:reviewer
n7:5P62O12MbDoeyIID4Kyrng