dwbp-ISSUE-178: The definition of duv:Feedback needs to be reviewed because it is not clear if it should be a subclass of oa:Annotation or just an instance of oa:Motivation. [Data Usage Vocabulary]
dwbp-ISSUE-179: The Working Group is considering to put all new classes and properties (together with the ones of the Data Usage Vocabulary) in the DCAT namespace. [Quality & Granularity Vocabulary]
dwbp-ISSUE-183: We may want to consider a revision of DCAT to make dcat:Dataset and dcat:Distribution subclasses of prov:Entity [Quality & Granularity Vocabulary]
dwbp-ISSUE-186: There might be no need for a subclass link between dqv:QualityMeasure and daq:Observation. I.e., we could re-use daq:Observation directly. [Quality & Granularity Vocabulary]
dwbp-ISSUE-187: Do we want to keep the same occurrence constraints as defined in DAQ (for example, that every metric should belong to exactly one dimension)? [Quality & Granularity Vocabulary]
dwbp-ISSUE-188: Section "Express the quality of a linkset" will be completed by examples coming from Riccardo's work on measuring the quality of linksets between SKOS concept schemes [Quality & Granularity Vocabulary]
dwbp-ISSUE-192: How to represent the relationship between a dataset and its different versions? Is PAV a good solution to track dataset versioning? [Best practices document(s)]