Re: Conflicts between Cube and DCAT in metadata properties (was: Re: AW: AW: [QB] Last Call document draft)

cygri wrote:

> Proposed steps for aligning the two specs:
>
> - recommend dc:title/description on qb:DataSet in addition to rdfs:label/comment

+1...Names are important; dc:title and dc:description will likely lead
to stronger, less ambiguous values for these fields.

> - recommend dc:issued instead of dc:date for creation date in Data Cube

+1...dc:issued implies "first appeared" and is better than "created,"
"published," etc....Also, dc:date could refer ambiguously to other
dates in the lifecycle.

> - Add a note to beginning of Data Cube Section 9 that says that other documents such as DCAT have additional recommendations for metadata properties.

+1...Good to specify connections between the recommendations like this.

> - make dcat:theme a subproperty of dc:subject in DCAT

+1...dc:subject is more intuitive and should be primary. dcat:theme
seems more dependent on interpretation...

> The result would be that if you follow the DCAT recommendations, you end up with something that matches the Cube recommendations, except for the use of a subproperty in the case of dcat:theme vs dc:subject.

Yes. Thanks, Richard!


-- 
John S. Erickson, Ph.D.
Director, Web Science Operations
Tetherless World Constellation (RPI)
<http://tw.rpi.edu> <olyerickson@gmail.com>
Twitter & Skype: olyerickson

Received on Friday, 8 March 2013 13:16:05 UTC