<?xml version='1.0' encoding='utf-8'?>
<response>
	<entry>
		<id>20110998</id>
		<hash>eb73c5b84f7508ddcc3883c2cdb458c8</hash>
		<requestHash>bridgewright</requestHash>
		<profileUrl>http://gravatar.com/bridgewright</profileUrl>
		<preferredUsername>bridgewright</preferredUsername>
		<thumbnailUrl>http://2.gravatar.com/avatar/eb73c5b84f7508ddcc3883c2cdb458c8</thumbnailUrl>
		<photos>
			<value>http://2.gravatar.com/avatar/eb73c5b84f7508ddcc3883c2cdb458c8</value>
			<type>thumbnail</type>
		</photos>
		<name>
			<givenName>Will</givenName>
			<familyName>Truax</familyName>
			<formatted>William Truax</formatted>
		</name>
		<displayName>Will Truax</displayName>
		<aboutMe>I&apos;m a timberframer and preservation carpenter, and regularly work on Covered Bridge restoration projects.

Bridgewrighting can be a tough row to hoe, for a myriad of reasons. From scheduling issues to differing opinions and philosophies on what is appropriate in methods and materials, to multiple jurisdictions still not sufficiently vetting bidders resumes - Which is to say, just because a company is on that state approved list and capable of building that seven figure overpass, this does not mean they are capable of restoring a wooden bridge...

So, I have much to say about all this and more - And despite my tough row observation, I promise not to whine.</aboutMe>
		<currentLocation>New Hampshire</currentLocation>
		<emails>
			<value>Bridgewright@ymail.com</value>
			<primary>true</primary>
		</emails>
		<accounts>
			<domain>linkedin.com</domain>
			<username>linkedin.com</username>
			<display>linkedin.com</display>
			<url>http://www.linkedin.com/pub/will-truax/40/466/529</url>
			<verified>true</verified>
			<shortname>linkedin</shortname>
		</accounts>
		<accounts>
			<domain>twitter.com</domain>
			<username>Bridgewright</username>
			<display>@Bridgewright</display>
			<url>http://twitter.com/Bridgewright</url>
			<verified>true</verified>
			<shortname>twitter</shortname>
		</accounts>
	</entry>
</response>
