W3C home > Mailing lists > Public > public-sdw-wg@w3.org > June 2017

Re: Re: Group endorses SOSA being taken up by schema.org

From: Dan Brickley <danbri@google.com>
Date: Fri, 16 Jun 2017 13:51:52 +0100
Message-ID: <CAK-qy=5i24c7jN5Ho98XLjzcdvwS6Se1t9j7AbjcGpk8k5yJgQ@mail.gmail.com>
To: "Svensson, Lars" <L.Svensson@dnb.de>
Cc: Simon Cox <Simon.Cox@csiro.au>, Armin Haller <armin.haller@anu.edu.au>, "SDW WG (public-sdw-wg@w3.org)" <public-sdw-wg@w3.org>
On 16 June 2017 at 13:43, Svensson, Lars <L.Svensson@dnb.de> wrote:

> On Friday, June 16, 2017 1:50 PM, Dan Brickley [mailto:danbri@google.com]
> wrote:
> > On the Google side regarding dataset discovery and
> > https://developers.google.com/search/docs/data-types/datasets we're
> currently
> > consuming basic DCAT (if expressed in json-ld, rdfa, or microdata) as
> alongside
> > Schema.org dataset descriptions in any of those. My sense is that much
> of the
> > vocabulary needed to improve the state of things is already around
> (CSVW, Data Cube,
> > DC, DCAT, Schema.org, SKOS, SOSA, QUDT, etc.), but there's a need to
> figure out
> > ways of combining them. So the likes of https://www.w3.org/TR/shacl/
> may prove
> > useful for capturing such patterns (as well as simple examples /
> documentation of
> > course). There is also btw some potential via JSON-LD context files to
> hide some multi-
> > namespace complexity via indirection, since the @context can map a
> seemingly flat set
> > of terms into several different "behind the scenes" namespaces.
> Sounds like a use case for profiles to me...

Yes, same ideas, and some common history eg see
http://dcpapers.dublincore.org/pubs/article/download/866/862 and
although I suspect the JSON-LD @context angle has been under-explored so
far. JSON-LD is a little less appealing for IoT scenarios than for dataset
discovery because it makes (graph-extraction) parsing dependent on the
contents of a remote file, and IoT often needs to operate offline and
without leaking signals to the outside world. But that's a discussion for


Received on Friday, 16 June 2017 12:52:29 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:33 UTC