arch-property-readable : The state exposed by a Property MUST be retrievable (readable).

[mlagally]

No description provided.

[benfrancis]

From #625 (comment)...

• arch-property-readable : The state exposed by a Property MUST be retrievable (readable). arch-property-readable : The state exposed by a Property MUST be retrievable (readable). #633

Conclusion: ❌ I wouldn't mind if this was true, but it clearly isn't true because there's a writeOnly member of PropertyAffordance.

---

Suggestion: Remove the assertion.

[sebastiankb]

There can be use cases that properties are defined only for writable purposes (eg, parameter settings) and other properties for readonly (e.g., read latest parameter settings). I think, it is not best practice and not really REST style. However, it does not hurt and at least would open the opportunity to retrofit existing implementations.

btw: I would be open to have a recommendation for the profile that says properties are always readable .

[mlagally]

arch call on 25.11.:
remove here, clarify in TD, consider mandating in profile

[sebastiankb]

PR clarifies the usage of readOnly and writeOnly in Properties in the TD spec w3c/wot-thing-description#1306 (review)

Assertation in Arch can be removed