-
Notifications
You must be signed in to change notification settings - Fork 6
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
product-type vocabulary URI #67
Comments
I guess it should explicitly mention the prepended " |
On Fri, Oct 22, 2021 at 04:20:34AM -0700, Mark Taylor wrote:
Section 3.2.9 describes the `content_qualifier` column and references
> the IVOA product_type vocabulary (currently at https://www.ivoa.net/rdf/product-type/)
This language is a bit different from that used in section 3.2.6 which references the core DataLink vocabulary; in particular it appears to give a dereferenceable URL explaining where to find the vocabulary content rather than the URI giving the vocabulary namespace - it uses the "https" scheme rather than "http".
@msdemlei can you take a look and reword if necessary? If you're happy with it then I'm sure it's OK.
All good points; given VocInVO 2, an overhaul of semantics was
necessary anyway.
PR #71 would give a unified approach to semantics and
content_qualifier.
|
mbtaylor
added a commit
to mbtaylor/DataLink
that referenced
this issue
Nov 5, 2021
Corresponds to changes from issue ivoa-std#67 and PR ivoa-std#71.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Section 3.2.9 describes the
content_qualifier
column and referencesThis language is a bit different from that used in section 3.2.6 which references the core DataLink vocabulary; in particular it appears to give a dereferenceable URL explaining where to find the vocabulary content rather than the URI giving the vocabulary namespace - it uses the "https" scheme rather than "http".
@msdemlei can you take a look and reword if necessary? If you're happy with it then I'm sure it's OK.
The text was updated successfully, but these errors were encountered: