- From: Christophe Guéret <christophe.gueret@dans.knaw.nl>
- Date: Fri, 8 May 2015 13:06:57 +0200
- To: Antoine Isaac <aisaac@few.vu.nl>
- CC: Public DWBP WG <public-dwbp-wg@w3.org>
Received on Friday, 8 May 2015 11:07:23 UTC
Hoi, I think we could merge the two reqs into one about describing to which extent the data is complete. For instance, surveys completness could be described via the description of they surveyed population. Christophe -- Sent with difficulties. Sorry for the brievety and typos... Op 8 mei 2015 09:11 schreef "Antoine Isaac" <aisaac@few.vu.nl>: > Dear all, > > Maybe this can be a part of my action: > ACTION-153: Look at completeness as one of the quality dimensions > > Should we continue to keep the two following requirements: > - R-DataMissingIncomplete: Publishers should indicate if data is partially > missing or if the dataset is incomplete > - R-QualityCompleteness: Data should be complete > > It seems that according to all we say on metadata best practice, if > there's a quality criterion then publishers should try their best to > publish metadtaa about it, and thus R-DataMissingIncomplete is redundant. > > Plus, in the current formulation of R-DataMissingIncomplete, I'm not sure > I grasp the difference between "data is partially missing" and "the dataset > is incomplete". > > What do you think? > > Best, > > Antoine > >
Received on Friday, 8 May 2015 11:07:23 UTC