Re: Invitation: Linked Life Data @ Weekly from 11:00 to 12:00 on Monday (HCLS)

Hi all,
 Here's the meeting info for today:

  --------------
Meeting URL
http://fuze.me/19537803

Toll / Intl #: +1 (646) 583-7415
Toll free #:
Attendee PIN #:  47479369
--------------


m.


On Mon, Apr 29, 2013 at 1:37 PM, Health Care Life Sciences <
w3.hcls@gmail.com> wrote:

>  more details »<https://www.google.com/calendar/event?action=VIEW&eid=cm1yMWZub29jN2Q4NjdqaTdkZmdma2RkOGMgcHVibGljLXNlbXdlYi1saWZlc2NpQHczLm9yZw&tok=MTcjdzMuaGNsc0BnbWFpbC5jb20zYjk2YjBjYjkyNGM0Zjg2MTZkYjJkZjZkMjg2Nzk1MTA4YTE0NmQw&ctz=America/New_York&hl=en>
> Linked Life Data
> This meeting will be held using fuze: please join at **Michel will send
> fuzebox info**
>
> Note: There have been various small hiccups with fuzebox so I recommend
> that you join ahead of time if you aren't sure about fuzebox working
> properly. I recently discovered that you will get *no message* if there is
> no Internet connectivity - it will simply do nothing when you start the
> local fuzebox client.
>
> Duration: ~1 hour
> (Variable) frequency: ~weekly
> Convener: M. Scott Marshall
>
> Session Theme: Metadata for data discovery and dataset description using
> SPARQL
>
> * a model for provenance, versioning, format and availability - Michel,
> Alasdair
> Relevant docs:
> the abstraction
> -
> https://docs.google.com/drawings/d/1e6qsxPkc-qKecVTJGJePE1Nuy2sD8Puu-FsEtUtGC-o/edit?disco=AAAAAFWHcnw
> sample implementation using chembl:
> - https://docs.google.com/file/d/0B4y0zfdRviKsS1l2NEttN3pfc1k/edit
> * Remaining metadata attributes in working draft - All (time allowing)
> - Working draft:
> -
> https://docs.google.com/spreadsheet/ccc?key=0Aoy0zfdRviKsdFJWTDFpblNXc3BtelhrdEpNYTdvbXc#gid=1
> * AOB
>
> **********************************************************************
>
> Michel and Alasdair have model proposal for a dataset version and
> formatting: thrashing out
> the final details and will present as the first item at the next call.
>
> Focus on provenance and origin:
>
> Version: literal
> Dates: Full date time with timezone
> Modified by: URI for a person
> Source: Needs to be present and specify the version/date of the source
> Prior version: point to URI
> Superseding version: Maintenance issue; can be inferred; provenance
> vocabularies
> only point backwards
> Subset/superset: only assert that you are a subset of another one
> Frequency of change: estimate; use a URI for the value, e.g. dublin core
> Latency of change: time it takes for changes in the raw data to appear in
> the derived
> dataset. Very specialised and probably not to be included
> created with: realised we need to point to a tool that was used to
> generate the dataset;
> particularly for D2R or Bio2RDF point to versions of scripts
>
> Aggregation of datasets is covered by source/derivation: simply include
> multiple sources
>
> Availability
>
> Availability: raises a maintenance issue; could capture available until X
> if it is known that
> it is no longer going to be available. Good for registry use case, but not
> necessarily for
> data publishing. It is a monitoring property.
> Publisher: need to decide a value set: literal/URI
> Format: mime type of the file, not the vocabularies used; EDAM, biosharing
> as
> candidates
> data item HTML template: to automate access
> RDF dump: available in multiple formats
> SPARQL endpoint
> API: point to a top level page about the API rather than each individual
> method
> Catlog/registry: point to records in registries. Inverse relationship with
> the registries
>
> *When*
> ********Weekly from 11:00 to 12:00 on Monday Eastern Time
> *Where*
> #hcls (map <http://maps.google.com/maps?q=%23hcls&hl=en>)
> *Calendar*
> HCLS
> *Who*
> •
> w3.hcls@gmail.com - organizer
> •
> public-semweb-lifesci@w3.org
> •
> dbcatalog
>
> Going?   **All events in this series:   *Yes<https://www.google.com/calendar/event?action=RESPOND&eid=cm1yMWZub29jN2Q4NjdqaTdkZmdma2RkOGMgcHVibGljLXNlbXdlYi1saWZlc2NpQHczLm9yZw&rst=1&tok=MTcjdzMuaGNsc0BnbWFpbC5jb20zYjk2YjBjYjkyNGM0Zjg2MTZkYjJkZjZkMjg2Nzk1MTA4YTE0NmQw&ctz=America/New_York&hl=en>-
> Maybe<https://www.google.com/calendar/event?action=RESPOND&eid=cm1yMWZub29jN2Q4NjdqaTdkZmdma2RkOGMgcHVibGljLXNlbXdlYi1saWZlc2NpQHczLm9yZw&rst=3&tok=MTcjdzMuaGNsc0BnbWFpbC5jb20zYjk2YjBjYjkyNGM0Zjg2MTZkYjJkZjZkMjg2Nzk1MTA4YTE0NmQw&ctz=America/New_York&hl=en>-
> No<https://www.google.com/calendar/event?action=RESPOND&eid=cm1yMWZub29jN2Q4NjdqaTdkZmdma2RkOGMgcHVibGljLXNlbXdlYi1saWZlc2NpQHczLm9yZw&rst=2&tok=MTcjdzMuaGNsc0BnbWFpbC5jb20zYjk2YjBjYjkyNGM0Zjg2MTZkYjJkZjZkMjg2Nzk1MTA4YTE0NmQw&ctz=America/New_York&hl=en>
> *    **more options »<https://www.google.com/calendar/event?action=VIEW&eid=cm1yMWZub29jN2Q4NjdqaTdkZmdma2RkOGMgcHVibGljLXNlbXdlYi1saWZlc2NpQHczLm9yZw&tok=MTcjdzMuaGNsc0BnbWFpbC5jb20zYjk2YjBjYjkyNGM0Zjg2MTZkYjJkZjZkMjg2Nzk1MTA4YTE0NmQw&ctz=America/New_York&hl=en>
>
> Invitation from Google Calendar <https://www.google.com/calendar/>
>
> You are receiving this courtesy email at the account
> public-semweb-lifesci@w3.org because you are an attendee of this event.
>
> To stop receiving future notifications for this event, decline this event.
> Alternatively you can sign up for a Google account at
> https://www.google.com/calendar/ and control your notification settings
> for your entire calendar.
>



-- 
Michel Dumontier
Associate Professor of Bioinformatics, Carleton University
Chair, W3C Semantic Web for Health Care and the Life Sciences Interest Group
http://dumontierlab.com