Extension : property definition

[clementcolin]

When considering a TileSet having a batch table nothing is said about the semantics of such data (what the data represents). This fails to respect the linked open data principle (how so?). In order to integrate a semantic description of data (some would dubiously call it metadata) present in the batch table, we could use a new specific extension as placeholder. The work involved by the creation of a new extension is similar to the one realized for thee temporal extension, that is

• [ ] define the data model (UML level)
• [ ] transpose that model to a json schema in py3dtiles
• [ ] integrate the usage of that extension in Py3dtilers (add a description, URI, for each semantic data)

Then on the client side

• [ ] encode the data model in JS
• [ ] realize the associated extension reader
• [ ] integrate that extension support in UD-Viz
• [ ] register the Extension

Eventually, disseminate that extension :

• [ ] publish the extension in itowns (when accepted promote the client side code to iTowns out of UD-Viz)
• [ ] publish the extension in Cesium 3DTiles repository