this is another ambiguity in the standard. IMO, Action instance MAY identify attributes when it is defined. For INFRA, that is the GFD.224 document where `suspend` has an attribute. The ambiguity here is in "standard" vs. "implementation". Can implementation omit an attribute defined in the standard? It is not clearly stated anywhere ... of course.
I would say that this is not a high-priority issue. Requests specifying an undeclared attribute will simply be rejected by the server. I can live with that.
Hi Alvaro,
this is another ambiguity in the standard. IMO, Action instance MAY identify attributes when it is defined. For INFRA, that is the GFD.224 document where `suspend` has an attribute. The ambiguity here is in "standard" vs. "implementation". Can implementation omit an attribute defined in the standard? It is not clearly stated anywhere ... of course.
I would say that this is not a high-priority issue. Requests specifying an undeclared attribute will simply be rejected by the server. I can live with that.