ISSUE-238: Should some of our properties be sub properties of a parent property?

Should some of our properties be sub properties of a parent property?

State:
CLOSED
Product:
Data Usage Vocabulary
Raised by:
Carlos Laufer
Opened on:
2016-01-19
Description:
Laufer wrote: Obs: Maybe it would be interesting to still have the old properties without the multiple domain (range) constraints, and the new ones as subproperties. In that way, the properties could be reused in different usages and feedbacks. But this can be discussed after the publication of this version of the document

Eric's thoughts
- A number of properties have been created to accommodate support for dcat:Distribution and dcat:Dataset. To avoid having multiple classes for the domain and range properties were duplicated such as duv:hasDatasetUsage and duv:hasDistributionUsage.

The question has been raised as to whether these should be sub properties of a property duv:hasUsage.
Related Actions Items:
No related actions
Related emails:
  1. Re: [Minutes] 2016-02-05 (from bfl@cin.ufpe.br on 2016-02-06)
  2. Re: [Minutes] 2016-02-05 (from ericphb@gmail.com on 2016-02-05)
  3. [Minutes] 2016-02-05 (from phila@w3.org on 2016-02-05)
  4. dwbp-ISSUE-238: Should some of our properties be sub properties of a parent property? [Data Usage Vocabulary] (from sysbot+tracker@w3.org on 2016-01-19)

Related notes:

Based on the 2-5-2016 meeting, all domains and ranges were removed. duv:hasFeedback, duv:hasUsage, duv:refersTo. replaced all properties that were specfic to Dataset and Distribution with general properties.

Eric Stephan, 11 Mar 2016, 05:12:54

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 238.html,v 1.1 2017/02/13 15:26:32 ted Exp $