Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Date

Discourse SEC calls

Participants

Goals

Discussion topics

Item

Presenter/Suggested by

Issue

Notes

Meta

5 min

Opening

USEFUL Jira RESOURCE: CRs I have not accepted.

SEC Jira board.

Main Agenda

15 min

openEHR platform release management.

Pablo Pazos

Thomas Beale

Currently we release at a Component level, e.g. RM 1.1.0, AM 2.2.0 etc. We don’t currently have a full ‘platform release’ mechanism. To take care of e.g. RM 1.1.0 needs at least BASE 1.0.4 or similar.

NB: general idea of the components in openEHR was to be loosely coupled, and have limited version inter-dependency.

  • Thomas Beale : possibly implementable with Github submodules. But how to define the platform release baselines?

15 min

Specification lifecycle management

Pablo Pazos

We don’t currently mark specs as Obsolete / deprecated etc, although we do have guidelines for this.

The old PDF specs probably should be taken offline? We can’t regenerate them, so can’t easily mark them as deprecated within the docs.

When do we deprecate RM, AM etc specs? Probably all pre-1.0.2 RM should be deprecated.

15 min

JSON schema update

Pablo Pazos

10 min

Physical SEC meeting?

All

Update

30 min

REST API update

Seref Arikan (Personal)

Sebastian Iancu

OpenAPI Strategy

Overview for REST API 1.1.0 work to be done

Progress:

  • xx

Issues:

  • relationship between REST API release and releases of payload, i.e. RM, AM etc.

Tips and Tricks

Hackers' Corner

Next SEC call

Outstanding topics:

Agenda items:

Notes

Action items

ALL - nominate in-house experts from your org for addition to SEC Expert Panel

  • No labels