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

Statements

Subject Item
n2:L8r2UmCaZCn55krWEJtLPw
rdf:type
rev:Review
schema:dateCreated
2010-11-17T00:00:00
schema:itemReviewed
n7:yQab5dxZzgBLTEHCw9V7_w
n5:funnyReviews
0
rev:rating
3
n5:usefulReviews
0
rev:text
I'm a pretty big fan of airports... I like to see how they are planned and figuring out the layout. It's interesting to see an old airport with a bunch of additions to it and how it evolves to serve its city. Charlotte-Douglas is ok in that it is an international airport and large enough to pretty much fly anywhere. It helps that it is a US Air hub, but it also hurts that it's a hub since it seems like it's pretty expensive to fly in and our of Charlotte. I've always praised their long term parking since it seems well done, and I use it a lot when I travel for business. However the last time I planned on leaving my car in long term, all the lots were closed and I had to park in the daily lot (which isn't too much longer), but the stress of driving around trying to find a spot was a bit much on top of trying to give enough time for checking in and security. They do have the new body scanners installed (within the last year I think) but now all the controversy has sprung up about the technology. I kinda get creeped out thinking about what kind of imagine I am putting up on the screen and who is looking at it-but I did it this last trip. Hopefully it doesn't have adverse health effect because that would be bad - I'd start opting for the "pat down" instead.
n5:coolReviews
0
rev:reviewer
n6:Ry1O_KXZHGRI8g5zBR3IcQ