Skip to content

Conversation

@dr-shorthair
Copy link
Contributor

Renamed vocab-dcat --> vocab-dcat-1

Added

  • DCAT --> vocab-dcat
  • vocab-dcat --> vocab-dcat-3

Simon Cox and others added 30 commits September 8, 2017 10:10
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)
@dr-shorthair
Copy link
Contributor Author

Check is failing.
Probably because w3c.json is updated automatically by W3C and should not be manually editted.

However, there is inconsistency with the set of vocab-dcat* entries.
The entry labelled "vocab-dcat' actually describes DCATv1 which also has an entry labelled "vocab-dcat-1", and the obsoleting labels are incomplete.
I've tried to disentangle it, but (unsurprisingly) my manual edits to w3c.json are rejected.

How can we get w3c.json fixed?

@tidoust is this on you?

Meanwhile, I'll make a simpler change only to biblio.json

@tidoust
Copy link
Collaborator

tidoust commented Nov 29, 2024

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, vocab-dcat-20120405 used to exist, but if you make vocab-dcat an alias of vocab-dcat-3, that entry will no longer exist because there is no 20120405 version under vocab-dcat-3.

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 vocab-dcat, but then switched to levels. In practice, there are two vocab-dcat:

  1. The vocab-dcat that now is vocab-dcat-1. That explains the clunky entries in Specref.
  2. The vocab-dcat that represents the series of specs and currently targets level 3. Specref does not undestand series. Essentially, what you're trying to achieve cannot be done today in Specref. There's no good way to say "vocab-dcat used to be level 1, but now is level 3".

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 vocab-dcat. In the meantime, I would suggest to leave things as is.

@tidoust tidoust mentioned this pull request Nov 29, 2024
@dr-shorthair dr-shorthair deleted the DCAT branch April 2, 2025 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants