Releases: Systems-Modeling/SysML-v2-API-Services
2022-02 M1
2022-02-m1 2022-02-m1
2022-01 P1
This is a patch to the 2022-01 release.
Fixed
- Addressed issues with compatibility to 2022-01 metamodel baseline.
2022-01
New
- Updated to 2022-01 metamodel baseline.
2021-12
New
- Updated to 2021-12 metamodel baseline.
2021-11
New
- Updated to 2021-11 metamodel baseline.
2021-10
2021-09
The changes in this release align the REST API pilot implementation to the revised submission of the Systems Modeling API and Services specification.
New
- Implement
putProjectById,deleteProjectById,deleteBranchByProjectAndId, anddeleteQueryByProjectAndIdAPI endpoints - Integrate all
Datarealizations, i.e. SysML types -Element,Relationship,Item, etc. - and API types -ExternalData,ExternalRelationship,ProjectUsage(see below) - such that they can be versioned and configuration managed analogously in aCommit. - Introduce
TagAPI concept and accompanying endpoints, i.e.getTagsByProject,postTagByProject,getTagByProjectAndId, anddeleteTagByProjectAndId - Introduce
ProjectUsageAPI concept that is used to declare usage dependencies on other Projects. By virtue of being aDatarealization it is fully integrated with API versioning and querying capabilities.
Fixed
Elementconcept is abstracted toDataElementIdentityis renamed toDataIdentityElementVersionis renamed toDataVersion
2021-08
2021-06
New
-
Updated to 2021-06 metamodel baseline.
-
The following endpoints can now produce JSON-LD
application/ld+jsonresponses, in addition to JSONapplication/json:getProjectspostProjectgetProjectByIdgetBranchesByProjectpostBranchByProjectgetBranchesByProjectAndIdgetCommitsByProjectpostCommitByProject
This is represented in the OpenAPI specification, i.e. the HTTP REST API PSM, which also allows the pilot implementation to be tested through the Swagger UI app by selecting
application/ld+jsonin theResponse content typedropdown menu in addition to any of the other methods of interacting with HTTP REST APIs.Note that this change additionally aligns the JSON and JSON-LD responses, most notably by renaming
Record::idtoRecord::@idwhich affects all lifecycle concepts as they specialize fromRecord. This change will require regeneration of provided clients and is backwards-incompatible.
2021-06 RC2
2021-06-rc2 2021-06-rc2