One more to fix in 1.0.0, accidental retention of platform language

[fugu13]

We had agreed to get rid of the platform only with activity object language and removed it from a table, but it stuck around in a requirements list.

"The platform property MUST NOT be used if the Statement's Object is an Agent or Group." needs to be removed (and really we should update the language for version to say "if the Statement's Object is not an Activity", since it doesn't make much sense for the other allowed values, too).

[andyjohnson]

#199 was the issue this was involved in, for reference. I'm very reluctant to make any changes around platform because we had it marked as TBD. We never had resolution other than we didn't want TBD in the spec. I don't think it causes significant harm or inconsistency leaving it how it is. It will probably be loosened in a future version, which is way harder than tightening it. Let's open a new issue and tag it as a 1.1. We will keep finding "one more" of these 1.0.0 changes and have to draw the line somewhere. We're going to be changing some of the narrative language of other sections as well and will likely encounter other 1.1 changes. That is my 2 cents on the issue.

[garemoko]

Looks like the wording change already got in. It currently says "The platform property MUST only be used if the Statement's Object is an Activity."

Agree with removing this, probably for 1.1

[andyjohnson]

This requirement will be deprecated in 2.0. In 2.0, any objectType can use the platform property.