ECS Core and ECS Extended

We’ve discussed creating a separation between the most stable and well understood fields (ECS Core) and the more experimental ones (ECS Extended). This issue is meant to have a discussion on how we should do this, and track the subtasks.

• Write documentation explaining the difference between the two
• Assign each field to one of the two levels (#133)
  • Add the appropriate markings in all of the schema/*.yml files
• Modify the scripts to support this new metadata about each field
  • Output Level instead of Phase in the csv
  • Output Level in a new column in the HTML
• Later, only if needed
  • Option to generate core only csv & template?
• … (comment below for any other suggestion)

[ruflin]

I think we should for now only focus on Core and Extended. Everything that should go into App or Protocol should for now just go into Extended. This reduces the complexity for now and we can still introduce more layers later if needed.

[ruflin]

I’m ok with the above visual approach. The main downside I see is that people coming to ECS will see core and extended directly together on their first visit, at the same time this could be a benefit too. We should just start with one version and then see how it evolves.