USEFUL Jira RESOURCE: CRs I have not accepted.
Progress - specs website
For now, remove 2nd sticky menu.
decide preferred approach
From XSDs (@Sebastian Iancu )
From BMM (Cambio)
KL, PB: Prefer single file for most tools;
PB: JSON-schema code generation - to hard due to polymorphism? Needs ‘anyOf’ or if/then/else constructs
SI: questions on best structure of JSON schema repo
KL: covariance in generics also an issue
Citations / Refs / managed lists
agree approach to requirements
solve ref constraints in AOM/ADL
solve ref following in AQL
solve flattened ‘retrieve’ Entries
IM: use UIDs more (need better explanation here?)
QUERY 1.1.0 release
Outstanding CRs in REVIEW:
BASE 1.2.0 release
Oustanding CRs in REVIEW:
AM 2.1.0 Release
Oustanding CRs in REVIEW (4)
XSD ‘v2’ question to be resolved prior to release.
Serial data formats
Improve SDF to procurement standard - see Erik’s Discourse discussion.
Agree to work on the SDF spec by minimally adding refs.
Better SDF / web templates now open src
Discourse thread for open discussion (Erik)
Discussion to run for a week; @Sebastian Iancu + @Erik Sundvall to work on resolved version.
REST Release 1.1.0
Revision history problem in REST API - see Discourse
@Seref Arikan noted example of real Compositions with 20k commits
@Ian McNicoll asked about formalising version compression or similar
@Matija Polajnar but better to have ‘missing versions' (in version id list) rather than hack via the backdoor.
Next SEC call
IAN: agenda item for next call: Reference following in queries;