You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 24, 2026. It is now read-only.
I've already resorted to using the shorter {VSchemaInDev.0} tag on published VersionMeta and VersionSchema web sites. These are intended to be equivalent to {https://Schemas/VSchemaInDev.0.xml}. I envision a set of official standard schemes to be stored on the VersionMeta web site and to also maintain a database of well-known-name/URI pairs for lookup.
Stake-holder organizations will be able to register their schema online and have a choice to self-host their schema or pay to store them on VersionMetal.org.
The VersionMeta spec needs to be updated to describe the two forms (WKN/URI) and how tooling should use them, including local cache behavior.
Define "well known" VersionMeta tags.
I've already resorted to using the shorter {VSchemaInDev.0} tag on published VersionMeta and VersionSchema web sites. These are intended to be equivalent to {https://Schemas/VSchemaInDev.0.xml}. I envision a set of official standard schemes to be stored on the VersionMeta web site and to also maintain a database of well-known-name/URI pairs for lookup.
Stake-holder organizations will be able to register their schema online and have a choice to self-host their schema or pay to store them on VersionMetal.org.
The VersionMeta spec needs to be updated to describe the two forms (WKN/URI) and how tooling should use them, including local cache behavior.