Add revision counter to project object

[acusworth]

I would like to suggest that the schema be extended to add a version or revision counter of some kind that would allow people to update existing models and track which revision they're on. I don't feel it needs to be a mandatory field but could be helpful to some.

For now I can use attributes to store this info but, thought it might make sense to track as part of the schema design.

Sample:

project:
  name: Test project
  id: test-project
  description: This is a test project for the OTM development
  owner: John Doe
  ownerContact: john.doe@example.com
  revision: 1
  attributes:
    filePath: “file.xml”
    cmdbId: MyApp123

[jmgarcia-iriusrisk]

Hi @acusworth , thanks a lot for your feedback!

We’ve reviewed this internally, and since a revision counter may apply to certain projects depending on how the schema is being used — but not in a general way across all OTM cases — we believe it’s best to keep it stored in the attributes section of the schema.

Thanks again for your interest in the Open Threat Modeling Format! We’d really appreciate it if you could share in which situations or use cases you’re applying the schema — this helps us better understand how it’s being adopted in practice.

Kind regards,
Juan