- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Feb 2019 22:02:39 +0000
- To: public-dxwg-wg@w3.org
@makxdekkers , yes, this could be an option. However, after further review, I wonder whether we should change the approach, for a couple of reasons: 1. The current text denotes as "recommended" the properties specific to that class, and then lists those inherited from the parent class(es) (if any). I am afraid this approach can be misunderstood - i.e., a reader may think that the only important properties are the first ones (I mean, the only ones needed to document that resource type), and the other ones are not necessary. This is obviously not true. E.g., for [`dcat:Catalog`](https://w3c.github.io/dxwg/dcat/#Class:Catalog), the properties listed as "recommended" are "catalog record, hasPart, dataset, service, catalog, homepage, themes". But properties like title and description are equally (or even more) important. 2. The "recommended" properties do not include all of those defined in DCAT 2014: in this case, a reader may have the impression that we recommend against their use. Based on that, my suggestion is as follows: - Include in the set of "recommended" properties all those properties we think are relevant for documenting a given class, irrespective of whether they are specific to that class, or inherited from parent class(es). - State in a non-normative part of the same section that, for documenting that resource, it is possible to use, in addition to the "recommended" ones, those associated with the parent class(es) and not listed earlier. -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/766#issuecomment-464896957 using your GitHub account
Received on Monday, 18 February 2019 22:02:45 UTC