So far the Pieces length, MetaURL priority and URL priority use xsd:integer.
Yet none of these defines an applicable range. What that means is that negative values would be valid as well according to the draft even if they made no sense at all. In fact for the Pieces length this is probably not the case as the description in the draft should be enough to provide a positive range. So in my opinion we should either add a range or change them to one of the unsigned PODS. In that case we still have to define that 0 is not to be used for pirority. In terms of priority I would opt for a range as imo a priority of 268435456 would rather be confusing if it was also shown to the user not just used internally. We could use xsd:unsignedByte for example, when we would have only positive values and automatically a range (if we exclude 0 in fact) from 1 to 255. What do you think on that? Cheers, matthias
signature.asc
Description: This is a digitally signed message part.
