- From: Bernadette Farias Lóscio <bfl@cin.ufpe.br>
- Date: Mon, 4 May 2015 13:31:44 -0300
- To: Joao Paulo Almeida <jpalmeida@ieee.org>
- Cc: "public-dwbp-wg@w3.org" <public-dwbp-wg@w3.org>
- Message-ID: <CANx1Pzysx57S4rgPnzCztw9Wyy5puNF0rDYxOeU4wSMJJ+_=hw@mail.gmail.com>
Hi João Paulo, Thank you very much for your review and comments! My comments are below. > 1) In my opinion duv:Publisher should not be a notion defined in DUV > because of a matter of conceptual scope. The notion of “publisher" is used > in DCAT borrowed from DublinCore Terms. See > http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=terms#terms-publisher > > > DCAT does not specialize dct:publisher. It only adopts it informally > (suggesting that it should range over foaf:Agent with domain dcat:Dataset. > (I think that it would have been better to include publisher formally in > DCAT as a subPropertyOf dct:publisher, but this was not done in DCAT…) A > minor problem that we have to address is that dct:publisher’s range is > dct:Agent and not foaf:Agent, which I understood we intend to use in DUV. > I agree with you! In this case, we're gonna have dct:publisher as a property instead of a class. Maybe, we can also adopt dct:Agent instead of foaf:Agent to solve the dct:publisher's range problem. > > 2) With respect to duv:Consumer, this is certainly in scope, but I > believe this should be represented as some relation between an agent and a > Dataset. Either because it produces an application that refers do some > dataset or because the agent cites some data. So, if we are consistent in > our representation style, and considering (1), there should be no class for > Consumer, but instead, properties relating an Agent to the dataset it > cites, or an Application to the dataset it uses. Another option should be > to make duv:Consumer the range of properties that represent this. > I agree and I think it makes more sense! If dct:publisher is a property, then I think we should also consider duv:consumer as a property instead of a class. > > 3) What is the semantics of DatasetUsage and why it “provides" a Dataset > while an Application (a special kind of DatasetUsage) “consumes” a Dataset? > I think there is an error in the model and we shouldn't have a relation between DatasetUsage and Dataset. > > 4) Why is Citation not a kind of DatasetUsage? > Initially, Citation was a kind of Dataset Usage, but we changed and created a different class. We are still not sure about this relation between Citation and DatasetUsage. Our initial idea is that you use Citation to mention/cite that a specific dataset was used. On the other hand, datasetUsage should give an explanation about how the dataset was used. > > 5) I agree with others that “Blog” should not be a subclass of Feedback. > ok! We are still thinking about this :) Cheers, Bernadette > > best regards, > João Paulo > > -- Bernadette Farias Lóscio Centro de Informática Universidade Federal de Pernambuco - UFPE, Brazil ----------------------------------------------------------------------------
Received on Monday, 4 May 2015 16:32:33 UTC