IW Meeting 2013-09-05

From Inference Web

Jump to: navigation, search


Meeting Information



Meeting Preparation

Around the room

* Add a section for yourself 2 hours before meeting.
* Mark any discussion point that you would like to raise during meeting (with DURING MEETING). 
* Otherwise, assume that others will read the rest before meeting. 
* Also, please be considerate and read others' discussion points before the meeting starts.


  • The query that I mentioned last week is here. It finds all named graphs "unsummarized" that have not yet been summarized by another named graph "summary". The "summary" named graphs are derived from the "unsummarized" named graphs.
    • This is part of Prizms' new infrastructure for derived secondary datasets.
    • Next step is to find summaries that are out of date, i.e. summaries that were prov:generatedAtTime after the named graph was loaded (since we record the provenance of named graph loads).
  • Looking forward to knocking out the spreadsheet with Cynthia today. Though, it appears that work is finally blocking google docs.

A question to the group about the meaning of the following statement. By invoking AlchemyAPI with the URL http://inference-web.org/wiki/IW_Meeting_2013-09-05, we find out that the page is related to the PROV ontology. If we qualify (aka reify) the dcterms:relation triple and attribute it to alchemyapi.com, are we saying that 1) they caused this page to be related to PROV, or that 2) they influenced the statement that this page is related to PROV. The former can't be true, since Tim was the one that wrote it and actually influenced this page to be related to PROV. But, it'd be nice to say both and be able to distinguish between these influences.

  dcterms:relation <http://www.w3.org/ns/prov#>;
  sio:has-attribute :iw_meeting_relating_to_PROV;
   a sio:Attribute, dcterms:relation;              # (Also, think "rdf:Statement" with an implied "rdf:predicate dcterms:relation")
   sio:refers-to <http://www.w3.org/ns/prov#>;   # (Also, think "rdf:object")
   prov:wasAttributedTo <http://alchemyapi.com>;
<http://alchemyapi.com> a prov:Agent .

The example is motivated by trying to conform to AlchemyAPI's usage restrictions:

"""Users of the AlchemyAPI Free service tier must provide proper attribution within their website or application:

Provide a clickable hyperlink to www.alchemyapi.com with the text "Text Analysis by AlchemyAPI" within your website or application; and

Provide attribution to AlchemyAPI within any published works that are based on or mention AlchemyAPI, or content generated by AlchemyAPI, including but not limited to research papers and journal articles.

Provide attribution to AlchemyAPI within all web pages or documents where AlchemyAPI content and/or API results are used or displayed.""" -[1]









Facts about IW Meeting 2013-09-05RDF feed
Date5 September 2013  +
Personal tools