[poe] Issue: Should vs must in some odrl:LeftOperand marked as Vocab

riannella has just labeled an issue for https://github.com/w3c/poe as "Vocab":

== Should vs must in some odrl:LeftOperand ==
The usage notes on some LeftOperands are very inconsistent regarding the use of **must** vs **should**

In [count](https://w3c.github.io/poe/vocab/#term-count) the note says

> Should be a positive integer

When would it be OK to use a negative integer?

In [dateTime](https://w3c.github.io/poe/vocab/#term-dateTime) the note says

> Right operand should be a xsd:date or a xsd:dateTime, Value must conform to [iso8601] as represented in [xmlschema11-2]. The use of Timezone information is strongly recommended.

In what cases would it be OK not to use an xsd:date or an xsd:dateTime? And can I use any datatype as long as the representation conforms to xsd?

In [delayPeriod](https://w3c.github.io/poe/vocab/#term-delayPeriod) the note says

> Value must conform to [iso8601] as represented in [xmlschema11-2] as a xsd:duration. This maybe used with the odrl:andSequence operator. 

Why is the use of xsd mandatory here but only recommended in dateTime? (And the text should read "This may be used ..."; a common typo throughout the document)

In [meteredTime](https://w3c.github.io/poe/vocab/#term-meteredTime) the note starts with 

> The value must conform to ...

whereas in [payAmount](https://w3c.github.io/poe/vocab/#term-payAmount) the note starts with

> The datatype of the right operand...

It would increase readability if all instances where values **must** conform to certain datatypes were phrased the same way.

See https://github.com/w3c/poe/issues/150

Received on Saturday, 29 April 2017 13:25:11 UTC