-
Notifications
You must be signed in to change notification settings - Fork 55
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
DCAT Issue 702 - Added ? to all refs not explicitly marked as normative #719
Conversation
|
||
<p> | ||
The detailed differences between the two documents can be seen <a href="https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2F2018%2FWD-vocab-dcat-2-20180508%2F&doc2=https%3A%2F%2Fwww.w3.org%2FTR%2F2018%2FWD-vocab-dcat-2-20181011%2F">here</a> | ||
and the list of all the changes since the previous version of DCAT in the <a href="#changes">Change History</a> section. | ||
</p> | ||
|
||
<h3 id="dcat_history">DCAT history</h3> | ||
<p>The original DCAT vocabulary was developed and <a href="http://vocab.deri.ie/dcat">hosted</a> at the Digital Enterprise Research Institute (DERI), then refined by the <a href="http://www.w3.org/egov/">eGov Interest Group</a>, and finally standardized in 2014 [[VOCAB-DCAT-20140116]] by the <a href="http://www.w3.org/2011/gld/">Government Linked Data (GLD)</a> Working Group.</p> | ||
<p>This revised version of DCAT was developed by the <a href="https://www.w3.org/2017/dxwg/">Dataset Exchange Working Group</a> in response to a new set of Use Cases and Requirements [[DCAT-UCR]] submitted on the basis of experience with the DCAT vocabulary from the time of the original version, and new applications not originally considered. A summary of the changes from [[VOCAB-DCAT-20140116]] can be found at <a href="#changes">Change History</a></p> | ||
<p>The original DCAT vocabulary was developed and <a href="http://vocab.deri.ie/dcat">hosted</a> at the Digital Enterprise Research Institute (DERI), then refined by the <a href="http://www.w3.org/egov/">eGov Interest Group</a>, and finally standardized in 2014 [[?VOCAB-DCAT-20140116]] by the <a href="http://www.w3.org/2011/gld/">Government Linked Data (GLD)</a> Working Group.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this one be normative?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 from me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So probably no ? or !, here, but add a mention in a normative section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exactly. But the ? can be kept. If a ref is included only once in a normative section, it will end up in the "normative references" section only, even though elsewhere is marked as non-normative.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i.e. no point in adding a ? or a ! to anything in an informative section. The only case that is significant is to downgrade to a ? within a normative section.
(That case was the one that I was fighting in the case of LDP but I guess I just got it wrong?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It appears that there is also a rule that references in a context with class="note" are informative by default, but can be promoted to normative with a !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you put class="informative" on the element for a non rec-track document, like UCR?
I guess so.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It appears that there is also a rule that references in a context with class="note" are informative by default, but can be promoted to normative with a !
Good to know
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually now I'm not sure if DCAT-2014 should be a normative ref, as it is the document that this one supersedes. Probably not - DCAT-2014 is an important part of the provenance, but will be replaced in-place by this one and the RDF implementation (which is in dcat.ttl
) ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reverted DCAT-2014 to non-normative ref
dcat/index.html
Outdated
</p> | ||
|
||
<p> | ||
This document does not prescribe any particular method of deploying data expressed in DCAT. | ||
DCAT is applicable in many contexts including RDF accessible via SPARQL endpoints, embedded in HTML pages as RDFa, or serialized as e.g. RDF/XML, N3, Turtle, or JSON-LD. | ||
DCAT is applicable in many contexts including RDF accessible via SPARQL endpoints, embedded in HTML pages as [[?HTML-RDFa]], or serialized as e.g. RDF/XML [[?RDF-SYNTAX-GRAMMAR]], [[?N3]], [[?Turtle]], or [[?JSON-LD]]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm. Again - I'd expect these to be normative
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried to make them as normative, but then I got an error from ReSpec saying normative refs cannot be in informative sections.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah - OK. Yes, I guess that makes sense.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK - I added a little material on DCAT 2014 to a normative section.
Locally defined elements are in the namespace <a href="http://www.w3.org/ns/dcat#">http://www.w3.org/ns/dcat#</a>. | ||
Elements are also adopted from several external vocabularies, in particular [[FOAF]], [[DCTERMS]] and [[PROV-O]] | ||
Elements are also adopted from several external vocabularies, in particular [[?FOAF]], [[?DCTERMS]] and [[?PROV-O]] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I'm misunderstanding here - all these should be normative refs. I thought that implied a ! not a ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 from me.
Sorry, but this first try of mine was not meant to determine what was normative or not, but just to see if putting the ? would have achieved the expected result. As I said above, I actually started trying to make some refs normative, but I got that error from ReSpec, so I gave up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW, @dr-shorthair , please note that some refs above (as FOAF), are ending up in the "normative references" section, as they were marked as such in one of the normative sections.
You can see the result here:
https://rawgit.com/w3c/dxwg/andrea-perego-fix-to-refs/dcat/index.html#references
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #702 (comment)
…rial on use of elements from external vocabularies to be moved to a normative section.
# Conflicts: # dcat/index.html
…replaced by this rec)
I've fixed a few conflicts in this PR, and now checking the diff with ED, I see that it has a list of properties in dcat:Catalog that actually correspond to the superclasses and should not be listed. I suspect this is due to some removal in another PR. Will remove them and then merge. |
Thanks, @dr-shorthair & @agbeltran . Just noting that ReSpec complains about one normative ref in a non-normative section: |
Trying to address #702 , and following the relevant discussion in today's (30 Jan 2019) DCAT subgroup meeting:
https://www.w3.org/2019/01/30-dxwgdcat-minutes (go to the end)
Preview here: https://rawgit.com/w3c/dxwg/andrea-perego-fix-to-refs/dcat/index.html#references