Skip to content

Releases: Systems-Modeling/SysML-v2-API-Services

2022-02 M1

28 Feb 01:28

Choose a tag to compare

2022-02 M1 Pre-release
Pre-release
2022-02-m1

2022-02-m1

2022-01 P1

15 Feb 15:11

Choose a tag to compare

This is a patch to the 2022-01 release.

Fixed

  • Addressed issues with compatibility to 2022-01 metamodel baseline.

2022-01

05 Feb 02:50

Choose a tag to compare

New

  • Updated to 2022-01 metamodel baseline.

2021-12

08 Jan 04:21

Choose a tag to compare

New

  • Updated to 2021-12 metamodel baseline.

2021-11

07 Dec 00:46

Choose a tag to compare

New

  • Updated to 2021-11 metamodel baseline.

2021-10

12 Nov 23:22

Choose a tag to compare

No functionality changes relative to 2021-09.

2021-09

14 Oct 23:45

Choose a tag to compare

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, and deleteQueryByProjectAndId API endpoints
  • Integrate all Data realizations, 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 a Commit.
  • Introduce Tag API concept and accompanying endpoints, i.e. getTagsByProject, postTagByProject, getTagByProjectAndId, and deleteTagByProjectAndId
  • Introduce ProjectUsage API concept that is used to declare usage dependencies on other Projects. By virtue of being a Data realization it is fully integrated with API versioning and querying capabilities.

Fixed

  • Element concept is abstracted to Data
  • ElementIdentity is renamed to DataIdentity
  • ElementVersion is renamed to DataVersion

2021-08

18 Sep 23:33

Choose a tag to compare

No functionality changes relative to 2021-06.

2021-06

03 Aug 04:22

Choose a tag to compare

New

  • Updated to 2021-06 metamodel baseline.

  • The following endpoints can now produce JSON-LD application/ld+json responses, in addition to JSON application/json:

    • getProjects
    • postProject
    • getProjectById
    • getBranchesByProject
    • postBranchByProject
    • getBranchesByProjectAndId
    • getCommitsByProject
    • postCommitByProject

    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+json in the Response content type dropdown 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::id to Record::@id which affects all lifecycle concepts as they specialize from Record. This change will require regeneration of provided clients and is backwards-incompatible.

2021-06 RC2

29 Jul 17:58

Choose a tag to compare

2021-06 RC2 Pre-release
Pre-release
2021-06-rc2

2021-06-rc2