v0.39.0

Changelog

• 1426f5d Merge pull request #78 from openvaultdb/ecb-pin-chain-sol
• 73fcec6 feat: verify blocked ECB metadata pin chain

v0.38.2

Changelog

• c4489d3 Merge pull request #77 from openvaultdb/ecb-cli-human-notices-v0201
• 17b42e4 fix: adopt published human source notices in CLI

v0.38.1

Changelog

• 47676a4 Merge pull request #76 from openvaultdb/ecb-cli-pin-synthetic-sol
• 67c9a1d fix: adopt published producer and require provider source notices

v0.38.0

Changelog

• 2a419e2 Merge pull request #75 from openvaultdb/ecb-dynamic-rights-preparation-sol
• 1588f74 feat: prepare dynamic publisher rights without enabling execution

v0.37.0

Changelog

• 6751a14 Merge pull request #74 from openvaultdb/ecb-meaning-model-registry-sol
• 6e7af9d feat: publish preparatory native ECB daily model and meanings
• 9270bf1 fix: pin ECB meanings to the landed core revision

v0.36.0

Changelog

• 70f8af7 Merge pull request #73 from openvaultdb/ovdb-cli-ecb-http-adoption
• 5b36a77 feat: adopt live HTTP mounts with explicit serve rights identity
• 18b5c8e fix: guard serve process cleanup and adopt provider evidence
• da83274 fix: reconcile HTTP catalogue and drain serve handlers safely

v0.35.0

Changelog

• ad70f61 Merge pull request #72 from openvaultdb/ovdb-http-resource-definition
• a5a7a8f feat: define blocked original HTTP publisher sources
• f34e8c1 fix: bind HTTP source rights and gate all admission code

v0.34.0

Changelog

• 497f2bd Merge pull request #71 from openvaultdb/ecb-publisher-rights-sol
• e53b1e5 feat: verify Publisher source data rights and raw declaration pins
• 90e529e fix: enforce canonical rights JSON keys and valid UTF-8
• cff7d95 fix: satisfy Publisher rights coverage and dependency CI gates
• 6716b11 fix: staticcheck QF1003 tagged switch in rights JSON walk

v0.33.1

What changed for publishers

• A meaning file with no concepts list is now refused, as the OVDB Directory refuses it. concepts missing, null, a mapping or text gives a meaning-concepts finding at the meaning file. An empty list is accepted, as the Directory accepts it.

One new rule value in --json: meaning-concepts. Exit codes and schema are unchanged.

Known gaps still open (Go accepts, the Directory refuses)
The check does not yet judge what is inside the model and meaning files as the Directory does: the ModelSpec file's version, entity and property rules; the shape of each concept and duplicate concept ids; the bindings of concepts to model entities and properties; and chains between concepts. Fixes are in progress, one family at a time.

Changelog

• af1e491 fix: refuse a meaning file with no concepts list, as the Directory does (#63)

v0.33.0

What changed for publishers

ovdb publisher check now understands a database descriptor (ovdb-database.json) listed in OVDB.md beside its manifest, and judges it as the OVDB Directory does. Before, the descriptor was judged as a second manifest and the repository was refused.

Accepted now

• A repository that lists one manifest and one descriptor in publish, when the two agree with each other. Five of the six repositories registered in the Directory (adventureworks, chinook, northwind, pubs, sakila) now pass at their registered commits. The sixth (employees) is still refused for its CC-BY-SA-3.0 licence.
• With a descriptor beside it, the manifest's discovery no longer has to be on the origin of its url.

Refused, each at the descriptor's own line

• Invalid JSON, a wrong format, a missing or empty id, localId, serverId, serverDbBaseUrl or apiUrl.
• id that is not the manifest's url; a localId outside the pattern; a server field on another host than serverId; a discovery that is not the manifest's.
• More than one descriptor, or a descriptor beside more than one manifest (a limit of this check).

What a pass means, and does not mean
Exit 0 means the files in the repository agree with each other and with the rules that can be checked offline. It does not mean the Directory accepts the repository: the check cannot see the registry record, the hosted server, or other registered databases. In particular it assumes the registry record names the descriptor listed in OVDB.md.

Known gaps in this version (Go accepts, the Directory refuses)

• A meaning file with no concepts list is accepted here; the Directory refuses it. A fix is in review (#63).
• The check does not yet judge the contents of the meaning file beyond its id, license and models: concept shape, duplicate concept ids and the bindings of concepts to model entities and properties are checked by the Directory and not here. Porting them is planned.

For --json consumers

• manifests now counts manifests only. A repository with a descriptor reports "manifests": 1, "descriptors": 1 where it reported "manifests": 2. descriptors is new and is omitted when zero.
• New rule values: descriptor-json, descriptor-format, descriptor-required, descriptor-id, descriptor-local-id, descriptor-url, descriptor-origin, descriptor-discovery, repo-descriptor.
• schema stays 1. Exit codes are unchanged.

Changelog

• a35af94 feat: judge a database descriptor beside its manifest as the Directory does (#62)