search

linkml / prefixmaps

Semantic prefix map registry
https://linkml.io/prefixmaps/
Apache License 2.0
10 stars 3 forks source link

Schema.org recommends https, but validation fails because this requires http #73

Open vorburger opened 4 days ago

vorburger commented 4 days ago

In the context of https://github.com/enola-dev/enola/issues/757, I've just run into:

/home/vorburger/git/github.com/enola-dev/enola/docs/models/enola.dev/files.linkml.yaml
  warning  Schema maps prefix 'schema' to namespace 'https://schema.org/' instead of namespace 'http://schema.org/'  (canonical_prefixes)

According to https://schema.org/docs/faq.html#19, both https://schema.org and http://schema.org are valid... and the (current) canonical definition at source is actually using https already and not http (anymore, I guess) - so for a new schema, I'd like to use https.

It's http here, but https here, but that doesn't seem to be loaded or used? (I'm not sure how this relates to #26 ?)

According to https://linkml.io/linkml/schemas/linter.html#canonical-prefixes, I suspect I could somehow overwrite this via prefixmaps_contexts, but I haven't understood how, yet.

I'll just work around it by disabling that lint rule entirely in the meantime.

vorburger commented 4 days ago

I'll just work around it by disabling that lint rule entirely in the meantime.

FTR: That causes a lot of ("ugly") WARNING:Namespaces:schema namespace is already mapped to https://schema.org/ - Mapping to http://schema.org/ ignored.