Support WoT Things description for representing data about historical-datastore HOT 4 CLOSED

Since WoT is meant to describe how to interact with things rather than how to store their data, it may be better to keep it out of HDS. We can instead implement a WoT registry as a standalone component (perhaps as the new Resource Catalog API) with Thing Descriptions including properties of DGW and HDS endpoints (as the example above).

The separation of concern helps in:

• keeping HDS codebase and functionality to storage only
• independent development and deployment of WoT registry and HDS
• use of WoT registry without storage functionalities

from historical-datastore.

It is still not clear. which of the following are you proposing?

• No registry for HDS at all. An independent Resource Catalog (RC) will store all the metadata in WoT TD format.
• There is a registry for HDS which stores HDS data in WOT TD format+ there is a separate Resource Catalog that stores all the resources including HDS streams (in WOT TD format).
• There is a registry for HDS which stores HDS data in non-standard format (Current state) + there is a separate Resource Catalog that stores all the resources including HDS streams (in WOT TD format).

from historical-datastore.

Last option.

from historical-datastore.

Okay. makes sense. closing the issue. We need a strategy for a registrator which takes care of registration of new streams in HDS in the Resource Catalog and does the bookkeeping in order to keep the HDS Registry and the RC registry consistent with each other.

from historical-datastore.