TS-0001: Incorrect RW/RO/WO for "creator" attribute in almost all resource types

TS-0001 defines the following behaviour when creating a new resource (clause 10.1.2, step 7):

The Receiver shall check whether a creator attribute is included in the Content parameter of the request. If included, the creator attribute shall not have a value in the Content parameter of the request. If the creator attribute is included in the request and the creator attribute is supported for the type of resource being created, then the Receiver shall include the creator attribute in the resource to be created. The Receiver shall assign a value equal to the value carried in the From request parameter. In the event that the originator provides a value for the creator attribute within the request, this request shall be deemed invalid.

On the other hand if the creator attribute is not included in the Content parameter of the request, then the Receiver shall not include the creator attribute in the resource to be created.

Similar instructions are present in TS-0004 clause 7.3.3.5 .

TS-0004 correctly defines the request optionality of the creator attribute for most resources (ie. there are a few exceptions) as O/NP.

However, in TS-00001, the optionality is almost always stated as RO in the resource type definitions, which is not correct, because O/NP is WO.