Skip to content

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

2021-09

14 Oct 23:45
Compare
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
Compare
Choose a tag to compare

No functionality changes relative to 2021-06.

2021-06

03 Aug 04:22
Compare
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
Compare
Choose a tag to compare
2021-06 RC2 Pre-release
Pre-release
2021-06-rc2

2021-06-rc2

2021-06 RC1

15 Jul 14:20
Compare
Choose a tag to compare
2021-06 RC1 Pre-release
Pre-release
2021-06-rc1

2021-06-rc1

2021-05

14 Jun 17:03
Compare
Choose a tag to compare

New

  • Updated to 2021-05 metamodel baseline.

Fixed

  • Added Project#defaultBranch to the OpenAPI specification and client libraries.

2021-05 RC1

07 Jun 16:49
Compare
Choose a tag to compare
2021-05 RC1 Pre-release
Pre-release
2021-05-rc1

2021-05-rc1

2021-04

18 May 16:47
Compare
Choose a tag to compare

New

  • Introduced branching capability to enable multiple commit histories. This adds a number of new endpoints to create, read, and update branches, e.g. projects/$project_id/branches. It additionally integrates with the commit creation allowing for a commit to be added to a branch. Refer to specification document for details.
  • Updated to 2021-04 metamodel baseline.

Fixed

  • Commit#containingProject renamed to Commit#owningProject
  • Query#containingProject renamed to Query#owningProject
  • Removed GET projects/$project_id/head in favor of branching. To get the id of the head commit of the default branch of a project:
    • GET projects/$project_id and obtain the defaultBranch.id from the response
    • GET projects/$project_id/branches/$branch_id and obtain the head.id from the response

2021-04 RC1

05 May 05:11
Compare
Choose a tag to compare
2021-04 RC1 Pre-release
Pre-release
2021-04-rc1

2021-04-rc1

2021-03

14 Apr 02:21
Compare
Choose a tag to compare

New

  • The default Accept for requests, i.e. the content type of the response when not specified in the request, has been changed from application/ld+json to application/json. Clients desiring responses in JSON-LD can receive it by specifying the header appropriately, e.g. Accept: application/ld+json.
  • Updated to 2021-03 metamodel baseline.