-
Notifications
You must be signed in to change notification settings - Fork 47
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
small editorial change for dcat:Catalog definition #1188
Conversation
I like the generalization, but is it consistent with DCAT as a Data Catalog specification? |
Due to DCAT's history, there is an implication that the catalog resources will be somewhat related to data, but in reality So, I am in favour of generalising and go with Riccardo's definition, giving datasets and data services as examples. |
(@riccardoAlbertoni , editorial changes are fine indeed, as long as everyone do see them as editorial...) |
I think we did talk about it when
|
My apologies for reacting so late, but I'm not sure about "cataloged" in the proposed defintion:
If we are defining what a catalog is, we shouldn't use a related notion / word (what is a "cataloged resource"?). I suggest we drop "cataloged" and revise the definition with something like:
|
Perhaps we also need to add the 'single agent' as per "A dataset is a
collection of data, published or curated by a single agent. "
Also, doesn't the "curated" apply more to the datasets where the metadata
passively reflects the active changes to the datasets/services?
…On Tue, 7 Jan 2020, 22:08 Andrea Perego, ***@***.***> wrote:
My apologies for reacting so late, but I'm not sure about "cataloged" in
the proposed defintion:
A curated collection of metadata about cataloged resources (e.g., datasets
and data services)
If we are defining what a catalog is, we shouldn't use a related notion /
word (what is a "cataloged resource"?).
I suggest we drop "cataloged" and revise the definition with something
like:
A curated collection of metadata about a given set of resources (e.g.,
datasets and data services)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#1188?email_source=notifications&email_token=AAIFYTCE32UI3DGSS3T7CTLQ4T4MBA5CNFSM4JV5KBFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIKOS6Q#issuecomment-571795834>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIFYTAQHO2IDHA6YTWVZHTQ4T4MBANCNFSM4JV5KBFA>
.
|
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 am dropping "cataloged" in Italian, Spanish, and English.
As far as I understand, the primary concern of issue #1186 is rephasing the definition of catalogs so that it does not seem conflicting with the catalogs having other resources than data services and datasets. I have dropped the "cataloged" as suggested by @andrea-perego as I think the resulting sentence is enough to address issue #1186.
Supposing at this stage of the process we are still allowed to make small editorial changes, this PR tries to consider the suggestion made in issue #1186.
The former definition of dcat:Catalog
is revised in
Is this a good rephrasing for the other editors/ contributors?
I suggest finding an agreement on the exact sentence before touching any of the RDF files, as even if this is a small change, it implies adjustments in the translations provided as the rdfs:comment and skos:definition and impacts on the different RDF serializations.