22/Idset String Representation¶
This specification describes a compact form for expressing a set of non-negative, integer ids.
Editor: Jim Garlick <firstname.lastname@example.org>
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
It is often necessary to represent a set of non-negative, integer ids as a compact string for human input, output, or in messages. For example:
A set of task ranks.
A set of broker ranks.
A set of resource ids or indices.
An idset SHALL consist of unique, non-negative integer ids.
An idset string SHALL consist of ids in ascending numerical order,
delimited by commas, e.g.
Ids in an idset string SHALL be represented in decimal form.
Ids in an idset string SHALL NOT include leading zeroes.
Consecutive ids in an idset string MAY be compressed into hyphenated
An idset string MAY be surrounded by square brackets to promote readability,
An idset string SHALL consist only of the following characters:
The decimal digits:
0 1 2 3 4 5 6 7 8 9