Should clients parse ID's, e.g. of jurisdiction/state?


#1

Are IDs intended to be parsed, or should they be considered opaque to the client?

There’s sometimes information embedded there that clients will want that’s not otherwise available. For example, state id’s like ocd-jurisdiction/country:us/state:az/government have the two-letter state abbreviation embedded, which is pretty ubiquitously used outside of OpenStates as a state ID - not to mention in the V1 API. IIRC, districts (DivisionNodes) are similar.

If ids are intended to be opaque, I’ll post an issue for a state_id field.


#2

It should be safe to parse division IDs & also we may add an abbreviation field within the API as I can see it being useful.