Defining an $id for the WCON JSON schema document would allow for easier revision control by third-party vendors and end-users. Moreover, it would allow for some amount of negotiation/switching off between parsers by third parties. Currently, the only option is to maintain separate versions or just track "latest" which makes coordinating updates with users more fraught.
Defining an
$idfor the WCON JSON schema document would allow for easier revision control by third-party vendors and end-users. Moreover, it would allow for some amount of negotiation/switching off between parsers by third parties. Currently, the only option is to maintain separate versions or just track "latest" which makes coordinating updates with users more fraught.