solidex

First, cleaning up types before porting data over. This aims to make types (and lists of values) easy to consume e.g. in solid-site. Replace enums with arrays (for easy enumeration in JS plus automatic types) Split vs. ( for the union). Are we happy with this terminology? (It matches solid-site's current notation.) Drop option for Packages. We discussed this a long time ago; I don't think there's a useful distinction between and . (I could still see calling the merged type ...) Switch from Unix timestamps to ISO date times Rename into . ?? Should we split into and ? It looks like is the one and only one used by resources. It's also used in one package, so I guess it could be listed twice... Add annotations and script for generating JSON schema! generates . Second, restructure to use individual JSON files in . is no longer in the repo but is still in the JSON export. Many more scripts.