Let validator handle url arguments too
Require node ~0.10.0
Nock seems to not intercept requests when the tests are run in
node 0.8, causing failures.
Merge pull request #7 from stenington/validate-by-url

Let validator handle url arguments too
Adds validateHosted, validateHostedUrl, and validateSigned to validate specific types
invert some if conditions to match code style better
A first attempt at validator.getAssertionGUID().

Still need to document how it works in the README, but for now you
can look at the tests.
Merge pull request #8 from stenington/validate-expected-type

Validate expected type
Changed getAssertionGUID() algorithm to output SHA256 hashes, not URLs.

@brianloveswords argued that the arbitrary signed-assertion protocol
has no way of actually prescribing a location that can be found
somewhere, which is true. So instead of representing the GUID as a URL,
we will represent it as a hex-encoded SHA256 hash.

If the assertion is hosted, the GUID will be:

  sha256('hosted:' + assertion.verify.url)

Whereas if the assertion is signed, the GUID will be:

  sha256('signed:' + assertion.uid + ':' + origin(assertion.verify.url))
v0.1.0

Adds validate by URL
Adds validate-by-type helpers
Project now requires node 0.10
Documented validator.getAssertionGUID() in README.md.
added example to end of README.
Merge branch 'master' into get-assertion-guid

Conflicts:
	index.js
Merge pull request #9 from toolness/get-assertion-guid

Added validator.getAssertionGUID().
clarified what 'validator' in the usage section of the readme refers to.
fixed documentation for getAssertionGUID().
Added docs for a doesRecipientMatch() function.
Add docs for validator.validate*() methods
Implemented validator.doesRecipientMatch(), changed its docs a bit.
Fixed typo in doesRecipientMatch's handling of 1.0 assertions.
fixed typo in readme, info.structure -> info.structures.