[Interop-dev] Round 2: Network Device Config JSON Schema

[Jernej Kos]

Hello!

On 08. 11. 2014 18:43, Nemesis wrote:
> For example, the agent on openwrt could return the JSON without the
> manufacturer attribute, but a library like netengine can add it on the
> server side.

Yes, it could be an additional human-readable description in case you
want to pass the JSON to apps that will not directly know how to process
the model/vendor identifiers (because they will not have a database ready).

But there should IMO be some text in the schema definition that would
say the model/vendor id is authoritative (so for example in case the
application is able to parse the model/vendor identifier, that should be
what identifies it, not the human-readable string provided in the other
fields).


Jernej

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://lists.funkfeuer.at/pipermail/interop-dev/attachments/20141108/b8bc5e44/attachment.sig>