You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For data exchange we currently support the machine readable "SpecObject" and "ASPEC" formats. While these are technically sufficient, they show their heritage over three predecessor tools (TReqs, ReqM2 and Allosaurus). They could be a lot more streamlined and user-friendly.
Implementation Idea
We should add a machine-readable exchange format with JSON, that is closer to who OFT sees the data, more compact and less convoluted than OSPEC and ASPEC.
Sample File
{
"$schema": "http://schemas.itsallcode.org/oft/oft_specitem_1.0.json",
"creationDate": "<ISO creation date>",
"oftVersionUsed": "<version of OFT that was used to create the file>",
"formatVersion": "1.0",
"specificationItems": [
{
"id": "...",
"title": "...",
"description": "...",
"rationale": "...",
"comment": "...",
"status": "...""covers": ["cover_id_1", "cover_id_2"],
"depends": ["dep_id_1", "dep_id_2"],
"tags": ["tag_1", "tag_2"],
"source": {
"file": "<path to source file>",
"line": <line in source file>
},
},
...
]
}
Situation
For data exchange we currently support the machine readable "SpecObject" and "ASPEC" formats. While these are technically sufficient, they show their heritage over three predecessor tools (TReqs, ReqM2 and Allosaurus). They could be a lot more streamlined and user-friendly.
Implementation Idea
We should add a machine-readable exchange format with JSON, that is closer to who OFT sees the data, more compact and less convoluted than OSPEC and ASPEC.
Sample File
Potential Libraries
The text was updated successfully, but these errors were encountered: