HCLSIG BioRDF Subgroup/Meetings/2011/02-14 Conference Call

From W3C Wiki
Jump to: navigation, search

Conference Details

  • Date of Call: Monday, February 14, 2011
  • Time of Call: 11:00 am Eastern Time, 4 pm UK, 5 pm CET
  • Dial-In #: +1.617.761.6200 (Cambridge, MA)

[Note: limited access to European dial in numbers below]

  • Dial-In #: + (Nice, France)
  • Dial-In #: +44.203.318.0479 (Bristol, UK)
  • Participant Access Code: 4257 ("HCLS")
  • IRC Channel: irc.w3.org port 6665 channel #HCLS (see W3C IRC page for details, or see Web IRC), Quick Start: Use http://www.mibbit.com/chat/?server=irc.w3.org:6665&channel=%23hcls for IRC access.
  • Duration: ~1 hour
  • Convener: M. Scott Marshall
  • Scribe: TBD


  • Vocabularies for describing provenance/metadata of named graphs - Lena, Jun
  • Datasets to request from NIF? - All
  • Microarray RDF, Getting started on the W3C note - All
  • AOB

Minutes and Notes

<mscottm> Scott: motivates provenance and metadata about a graph, referring back to previous discussions
<mscottm> ..not meaning to put you on the spot Jun but please explain the provenance vocabularies available for consideration
<mscottm> Goal: come up with some basic information to add to each named graph in HCLS about the graph URI
<mscottm> carry out the practice on the HCLS KB
<jun> http://www.w3.org/2001/sw/interest/void/#sparql-sd
<mscottm> Jun: Can use Dublin Core for some basic provenance
<jun> The Provenance Vocabulary
<jun> more specific than OPMV
<mscottm> http://open-biomed.sourceforge.net/opmv/ns.html
<jun> http://purl.org/net/provenance/ns
<jun> that's the link to the Provenance Vocabulary
<jun> http://www.w3.org/2001/sw/interest/void/#license
<ericP> jun, is there anyone from CC or science commons reviewing VoID?
<jun> no
<jun> if they are on the sw-list, they should have seen our call for comments. but maybe they are not on the list?
<ericP> there's a disjoint between the US and most of Europe re: copyright-ability of database data
<mscottm> off the top of my head: creator(s), author, ref to original data, software used to create RDF rendering, license, date of last update, vocabularies used,
<mscottm> ..label of RDF rendering (for UI/application), 
<ericP> ambiguous urls: <file:/etc/passwd> <file:/C%2A/autoexec.bat>
<mscottm> human-readable name of graph (candidates): skos:prefLabel , rdfs:label, ..
<mscottm> Eric: domain of SKOS prefLabel?
<mscottm> Scott: thinks it's SKOS object
<mscottm> Jun: No domain
<mscottm> URL's for original data and what predicate? 
<mscottm> Jun: best terms prob. from Provenance Vocab.
<mscottm> dc:author for RDF graph creator (Eric notes that DC implies that you are talking about a document)
<mscottm> Jun: (checks) void recommends using dublin core
<jun> no domain definitions for dcterms:creator
<Lena> regarding Scott's question, we have a "dct:issued" but not a "dct:modified"
<mscottm> thanks!
<Zakim> - +20416aaaa
<Zakim> - +1.206.732.aacc
* michael has left #hcls
<mscottm> Once we've checked these choices with others and tried it out on HCLS KB, we can add it to the best practices note
<mscottm> Summarizing the tentative choices:
<mscottm> label - skos:prefLabel, skos:altLabel
<mscottm> creator - dcterms:creator   (can be applied to both RDF graph creator and creator of original data)
<mscottm> date - dct:issued (when used on graph URI, means date of creation)
<mscottm> license - http://www.w3.org/2001/sw/interest/void/#license (check this with science commons)
* Lena has quit IRC (Quit: http://www.mibbit.com ajax IRC Client)
* matthias_samwald1 has joined #hcls
* matthias_samwald has quit IRC (Ping timeout)
<mscottm> source data - predicate from Provenance Vocab. with value of URL for original data
<mscottm> software used for RDF rendering - Software Ontology
<mscottm> vocabularies used in the RDF - list? of what type??
<mscottm> When selecting services or graphs, we would like to know which endpoints access (already) materialized graphs, as opposed to using procedural attachment or entailment regimes
<mscottm> ..we will want to know about materialization when we are concerned about performance