Release Notes¶
Version 0.3.0.dev0 (2022-??-??)¶
Version 0.3.0 (2022-09-27)¶
Capability for compound scales has been added
Compound UID format developed
Many more registry entries needed for examples
Spreadsheet tools provide a little help to build the registry
Version 0.2.0 (2022-07-08)¶
The M-layer register has been populated with a variety of entries to support examples
An API has been better established
A unit test suite is included
Continuous integration on github runs the unit tests and doctests
Documentation has been extended and includes examples of use and details about the current API
Building the Read The Docs documentation is automated on github
Version 0.1.0 (2022-04-11)¶
The M-Layer concept in JSON and Python code.
Roadmap¶
In version 0.2.x, the intention is to build up the basic M-layer structure in a collection of JSON files representing central-register information about scales, aspects, conversions, and castings. The aim is to assemble sufficient information to support a few use-cases. There is no intention to be comprehensive.
At the same time a Python API will be developed. This will support a suite of examples and client-side usability to be assessed.
Later versions will look at:
M-layer manifests that record the digital identifiers used in a dataset. Manifests would be intended to accompany datasets.
Multiple M-layer registers. Supplementary registers could hold records not available in a central register. This will provide a mechanism for growing the M-layer.
Strategies for constructing M-layer registry records will be developed. Logical relationships between many sets of units can be exploited to generate records algorithmically, but automatically including references to external information is more complicated.
Strategies for testing and validating M-layer records will be developed.