Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added questions about json-schema

...

  • Immediate needs between Core and Export services:  what are the appropriate options to avoid Java/Go issuses
  • Longer term, what should be considered the leading service to service communications protocols (outside of REST) and why?
  • Our RAML documents reference draft-03 of json-schema.org.  Some questions:
    • draft-06 is the latest, should we move?
    • Do the current Java microservices use the specified schema for validating JSON?
    • Should we be using the schema for automated testing validation?
    • Should be be using the "enum" construct (supported by draft-03)?

Domain Identifiers

  • How should concepts like Device or Addressable be uniquely identified?  Currently using unique name strings
  • How should persistent store identifiers be related/not related to these identifiers.

...

  • Copyright header – stays the same until LF has an alternative header and tool to provide
  • Enums & JSON – use strings in place of any language specific enums or Iota in JSON messages and serialize/deserialize as necessary in your language of choice.

...