Merge pull request #1 from adlnet/master

update fork with master
Accept 1.0 as 1.0.0

The spec has been talked about as 1.0 for a long time, and we've been shooting for (and succeeding) to allow 0.95 clients to continue to send statements with only an updated version header -- but we'd previously talked about updating it to 1.0.

If even a few pieces of content out there have done tried already (which they could have done before any 1.0(.0) systems exist by trying the 1.0 version header and falling back to 0.95 if rejected), it will be worth LRSs accepting 1.0 as 1.0.0. I don't see a downside, if one were to map 1.0 onto our new version scheme 1.0.0 is a logical equivalent.
DISCUSS: Activity versioning clarification

Took a stab at resolving: https://github.com/adlnet/xAPI-Spec/issues/29 , but I'm really not sure we need to list this non-requirement here.

It did come up as a point of confusion in Alexandria (resulting in this issue), so it may be worth including.
updated based on feedback

fixed typo, changed to "no behavioral implications" as suggested by @fugu13
Minor: MD linking to semver.org in a HTML table is broken (GitHub parser issue)
Fixes Issue #265
Merge pull request #272 from scara/v10_Make_GitHub_Happy_no_MD_Linking_In_HTML_Table

Minor: MD linking to semver.org in a HTML table is broken (GitHub parser)
Another minor issue with the Bookmarklet: XAPI header missing
Fixes Issue #266
Merge pull request #269 from bscSCORM/actversion

DISCUSS: Activity versioning clarification
Merge pull request #260 from bscSCORM/version

Accept 1.0 as 1.0.0
Merge pull request #273 from scara/v10_Bookmarklet_Missing_X_Experience_API_Version

Another minor issue with the Bookmarklet: XAPI header missing
Merge pull request #2 from adlnet/master

merge master into fork
added Pankaj Agrawal to contributors
Merge pull request #278 from ljwolford/master

added contributor
Merge branch 'master' of https://github.com/adlnet/xAPI-Spec
clarify interaction component id to avoid type-practice conflicts making it impossible to use and still be valid
clarify attachments and behavior surrounding them
detail behavior of statement in context. This is the only change to the standard that breaks forwards compatibility, but as far as is known there are no non-test statements that use the broken behavior
clarify conversion behavior around context:statement
Merge pull request #279 from fugu13/interactioncomponentidfix

Interaction Component ID Fix
Merge pull request #281 from fugu13/contextstatement

Restrict context:statement to StatementRef