This schema allows clients to forward interesting entries from the "Commander's Log" Journal to EDDN - i.e. "Docked", "FSDJump" and "Scan" entries. The schema is based on pre-release info so this PR will likely need to be updated during the E:D 2.2 beta run.
About the schema:
The schema is deliberately minimal - it doesn't try to describe the content of the journal entries. Clients are expected to pass the Journal entries through essentially unmodified (but see the following points).
Some properties from the "Docked" and "FSDJump" Journal entries have been marked as "disallowed" since they're specific to the Cmdr. The sender must strip these properties out of the journal entries before transmitting them over EDDN.
The various *_Localised properties have been marked as "disallowed" since they're redundant. The sender must also strip these properties out of the journal entries before transmitting them over EDDN.
The "Scan" journal entry contains a "BodyName" property like "Praea Euq NW-W b1-3 3 a", but no "StarSystem" property. Can listeners in all cases unambiguously split the "BodyName" into its system and body constituent parts? The sender must track the current system and add a "StarSystem" property to those Journal entries that lack it (i.e. "Scan" entries).
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.