* Renamed sha-2 and content-Type properties to sha2 and contentType for easier reference as properties
(many languages don't like - in property names)

* Added clarifying requirements
* Added requirement to include hash in each part's header, so receiver doesn't
have to guess which hash length to use when verifying

* Added an example
minor clarification:
"only send one copy" language only applies within a single message
Added flag to include/exclude attachments when retreiving statements
(trivial) updated example hash

Hash in the example was calculated improperly, updated with correct hash.
Removed 'authoritative' flag

Shouldn't be controversial, I think we talked about removing this in 0.95 but just forgot to.

For those new to the discussion: this is a holdover from when the LRS was "smarter" than it is now -- we've decided it's up to systems reading statement to decide how to weigh statements.
Merge pull request #86 from paul-esch/master

Rewrite of 4.1.2 Actor
Merge pull request #88 from bscSCORM/nonauthoritative

Removed 'authoritative' flag
Merge pull request #87 from bscSCORM/binary

Attachment example, clarifications, minor changes
Rewrite of 4.1.3 Verb

As a sort of ‘clean slate decision' I left out references to previous
versions of the spec. I feel this has only a historic meaning to the
limited number of people that are aware of / were involved in previous
versions of the spec. In anyone feels this should be included, leave a
comment.

Possible confusion: The description of the ID property says a URI should
be human-readable. Yet, "tag:example.com,2012:xQr73H" is given as an URI
example a little earlier and that is not very human-readable. Is this a
contradiction?