Sygn Data Format

In addition to understanding HowSygnWorks, we need to also hash out some sort of basic understanding of a common data format. While we don't want to be to terribly dependent upon any particular schema, a common set of domain-specific agreements about what a "SygnDocument" will look like will undoubtedly be helpful.

About the Data Format

To see a few example code blocks, examine "DataExamples." What follows is a

It makes sense to me to have a number of fields be part of a basic specification that aggregating servers should be able to expect as part of a profile, file.

While some "first level" options might severely limit the ability of an aggregating server to expand beyond their very specialized task that a particular kind of profile might provide, it might make sense to separate the tools that collect the aggregate data, from the tools which generate the output. By building output around a template system modifying the required and optional data fields becomes nearly trivial, and makes it possible to deploy this kind of technology in multiple situations.

Also the profile files would contain a PGP signature, which would verify the contents of the file/lampblack. Users could also include additional plain text outside of the YAML block if they wanted, though the parsers would generally drop all non-structured information on the floor.