-
Notifications
You must be signed in to change notification settings - Fork 147
DCAT versions and aliases #834
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Sync with Tobie
DCAT --> vocab-dcat vocab-dcat --> vocab-dcat-3
* Update WGS84 * rename NIMA version to WGS84-NIMA --------- Co-authored-by: Simon Cox <dr.shorthair@pm.me>
* Add keys and patterns for ISO and OGC standard numbers (similar to IETF RFC numbers) * Need to double escape backslash in JSON pattern * Add option for /IEC as part of isoNumber * Add ISO numbers and OGC numbers for some existing entries * Add OMS and O&M (OGC and ISO standards) * Added new versions of GML * Fixed duplicated URL * Add GeoSPARQL 1.1 * OMXML and SensorML * Unbalanced parenthesis * stray comma :-( * Restructure GeoSPARQL version chain * Update WGS84 * rename NIMA version to WGS84-NIMA --------- Co-authored-by: Simon Cox <dr.shorthair@pm.me>
* Fix SMIL20 aliases and overwrite rules for media-source I'm working with @deniak on improving the data in the W3C API so that Specref may more easily switch to the W3C API. One rippling effect is that this means that some of the hacks done to get the right entries are no longer needed (and now create duplicates). Adjusting the rules accordingly. * Add updated w3c.json (That's the result of running the W3C script. Needed for tests to pass)
|
Check is failing. However, there is inconsistency with the set of vocab-dcat* entries. How can we get w3c.json fixed? @tidoust is this on you? Meanwhile, I'll make a simpler change only to biblio.json |
|
Build fails because there's a strict "any entry that ever existed must continue to exist" rule in place, and the update would drop entries that used to exist. For example, There is no easy way to disentangle this right now. This is triggered by the fact that DCAT started with using a level-less shortname
Once the W3C source has switched to the W3C API (PR #828), it will be possible to consider adding support for specification series. That update will also disentangle a couple of entries à la |
Renamed vocab-dcat --> vocab-dcat-1
Added