- From: Bernadette Farias Lóscio <bfl@cin.ufpe.br>
- Date: Thu, 15 May 2014 16:22:02 -0300
- To: Laufer <laufer@globo.com>
- Cc: Carlos Iglesias <carlos.iglesias.moro@gmail.com>, Makx Dekkers <mail@makxdekkers.com>, DWBP Public List <public-dwbp-wg@w3.org>
- Message-ID: <CANx1Pzy5neGV0aWVsFotDLD8k_ykWApkwsAWY5UXd-EQdRb51g@mail.gmail.com>
Hi Laufer, Thanks for sharing your thoughts! I am not sure if we should consider data catalogues as data brokers. A data catalogue is just a tool that helps data publication and data access, and both data providers and data consumers may use this tool. Concerning the classification of metadata, I suggest to think in terms of datasets and distributions, as described in DCAT and proposed by Makx. Since you mentioned Open Data Ecosystem, I'm sending a paper that I wrote together with a colleague about this subject. The paper considers Open Data as a Service, but it also describes and idea about Open Data Ecosystem. kind regards, Bernadette 2014-05-15 11:35 GMT-03:00 Laufer <laufer@globo.com>: > Hi Bernadette, Carlos, Makx, all DWBP members, > > > > I created a page on the wiki, "Best Practices – Guidance on the Provision > of Metadata", where we can put the information about this topic. I took the > liberty to define a prefix in the subject of the e-mails related to these > discussions: [BP- MET]. > > > > I would like to expose some thoughts that I think are related to the data > on the web ecosystem. I see a kind of data architecture that has three big > roles: a data Publisher, a data Consumer and a data Broker. The Broker is > the one that has information that can be used by the Consumer to find data > published by the Publisher. > > > > As an example of Brokers we can think about implementations of CKAN, used > by data.gov, dados.gov.br, etc. CKAN has metadata (provided by > Publishers) that are useful for Consumers to find data. CKAN is a registry > and can also be a repository for the data to be consumed. Almost all use > cases of DWBP WG are examples of Brokers. > > > > At the same time, data published in CKAN implementations can have multiple > formats, as CSV, for example. Once a Consumer chooses some data to use from > a Publisher, she needs another kind of metadata to understand how to access > the data and its semantics. > > > > I propose to create categories and types of metadata. I see two > categories: metadata for search and metadata for use. Each of these > categories would have types of metadata. For example: > > > > Metadata Types for Search > > Human Content Description (free text) > > Machine Content Description (vocabularies) > > Provenance > > License > > Revenue > > Credentials > > Quality / Metrics > > Release Schedule > > Data Format > > Data Access > > > > Metadata Types for Use > > URI Design Principles > > Machine Access to Data > > API specification > > Format Specification > > > > The Brokers itself have another kind of metadata about its own information. > > > Maybe in the future a Consumer will search for data no more in these > Brokers (with its catalogues) but they will use search engines that could > obtain the metadata (both the search and the use) using its crawlers. But > now, we have this heterogeneous world of data that is one of the > characteristic of the web since its beginning. > > > > Contributions of all members of the DWBP WG will be appreciated. > > > > Best Regards, > > Laufer > > -- > . . . .. . . > . . . .. > . .. . > -- Bernadette Farias Lóscio Centro de Informática Universidade Federal de Pernambuco - UFPE, Brazil ----------------------------------------------------------------------------
Attachments
- application/pdf attachment: OpenDataAsaService-submitted.pdf
Received on Thursday, 15 May 2014 19:22:52 UTC