search

EURODEO / rodeo-edr-profile

This is a repository to make EDR profiles used in EURODEO visible for all use
https://rodeo-project.eu/rodeo-edr-profile
Creative Commons Attribution 4.0 International
2 stars 0 forks source link

bootstrap standard document #2

Closed tomkralidis closed 1 month ago

tomkralidis commented 1 month ago

Bootstrap of profile document. A PDF render is available here for reviewing in context.

havardf commented 1 month ago

Hm, we are probably going to have multiple profiles. As of now, I have a folder like profiles/observations. The standard documents is in a tree structure from the /standard folder. Do you have any thoughts on how to structure this? Multiple profiles in one document? Or multiple document structures?

tomkralidis commented 1 month ago

I would suggest a single profile document with 1..n Requirements Classes (and their associated Conformance Classes). I am guessing between observations, radar, etc., there will be some commonality between them that can act as the "Core" Requirements baseline. A single profile document would also reduce document/boilerplate overhead.

If we find that a single profile document becomes too large then we can break out accordingly.

havardf commented 1 month ago

I would suggest a single profile document with 1..n Requirements Classes (and their associated Conformance Classes). I am guessing between observations, radar, etc., there will be some commonality between them that can act as the "Core" Requirements baseline. A single profile document would also reduce document/boilerplate overhead.

If we find that a single profile document becomes too large then we can break out accordingly.

Sounds good. Not exactly sure what will be common across all profiles at the moment, but seems like a good initial plan.