All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Add createMethod.graphql as example of a mutation on the metabase #324
- Upgrade development packages to latest versions #285
- Use JSON Schema Draft 2020-12 and upgrade tooling #307
v1.0.0 - 2022-03-02
- Document previously undocumented database GraphQL schema #101
- Add more tooling for GraphQL schema, queries, and mutations #104
- Add query examples for
data
,allData
, andhasData
#105 - Add section to publication to be able to refer to just one part of a publication #155
- Add two examples of methods for daylighting and glare simulations #179
- Add version to JSON Schema
$id
s #188 - Add examples photovoltaicWithOptical #207, semitransparentBuildingIntegratedPhotovoltaicThermal #209, from ES-SDA #213 and dataFormatPdf #226
- Add the key
roughness
#205 - Add the position of coatings to components #223
- Add
currentVoltage
characteristics for modules #224 - Add release actions #281
- Add JSON schema for hygrothermal data #322
- Add example of double glazing including subcomponents #334
- Allow definition of switchable layers #339
- Improve propositions used in GraphQL queries to search for data #102
- Further align database GraphQL schema and JSON schema #103
- Flatten data HTTP resource trees to make them queryable with one query without having to know the trees depth #108
- Only use
additionalItems
for tuple validation and not for list validation, useuniqueItems
for lists of enumerated items, useconst
for one-valued enums, and don't have special this-property-has-no-value values for optional properties #110 - Improve titles and descriptions of identifiers, name
uniqueId
of decentral identifiersvalue
, and make identifiers be issued by databases instead of institutions #107 - Clean-up the stakeholder JSON schema, in particular, how stakeholders are referenced in specific roles #111
- Associate contact information and GnuPG keys with a person's and institution's affiliations #112
- Check and correct usages of
oneOf
,anyOf
, andallOf
#113 - Use specific instead of general and (almost) meaningless number definitions #114
- Improve titles and descriptions in the JSON Schema for optical data #115
- Improve documentation of approvals in the database GraphQL schema #117
- Clean-up Dockerfile, in particular, remove notes regarding Python #121
- Correct minor errors in database GraphQL API #173
- Name
dataId
uuid
, removevalidity
from*Data
andDataApproval
, use parent identifier instead of child identifiers to describe tree structure, do not require response approvals to be created on the fly #180 - Update GraphqL schema of metabase to match the current deployed version #280
- Rename organization to
building-envelope-data
and API repository toapi
#277 - Use acronyms to identify standardizers #154
- Use JSON Schema Draft 2019-09 and upgrade tooling #181
- Restructure
numbersWithUncertainty
to make the data less verbose#195,#216 - Improve the structure of geometry.json #205
- Improve the structure of calorimetricData.json #209]
- Correct the requirements of
emergenceDirection
#213 - Offer detailed definition of calorimetric fluxes #222
- Add categories to
material
,layer
andunit
from EN 12216 #223 and from EN 13024-1, EN 14179, EN 1863, DIN 18008-5 #224 - Add more mirrored values to
apis
#238 - Add spectrum
ultraviolet
for integral values and improve the optical examples #247 - Change propositions for lists and make parameter
where
optional #260 - Move
color
to theresults
of an optical data set #326 - Remove the shortcut
nodes
to reduce the implementation effort #318 - Describe codespaces as an option for Windows users #336
- Remove intermediate representation of optical data #152
- Remove custom directions from optical data #153
- Remove
validity
everywhere except ofmethod
which can depend for example on a standard #219
- Fix the three phase method test by using enumerated standardizers instead of identifiers #192
v0.1.0 - 2020-08-31
First major-version-zero release 0.1.0.
Note that according to Semantic Versioning Specification, Item 4,
Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.