BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/New_York:20130429T110000
DTEND;TZID=America/New_York:20130429T120000
RRULE:FREQ=WEEKLY;BYDAY=MO
DTSTAMP:20130429T123740Z
ORGANIZER;CN=w3.h...@gmail.com:mailto:w3.h...@gmail.com
UID:rmr1fnooc7d867ji7dfgfkd...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Health Care Life Sciences;X-NUM-GUESTS=0:mailto:w3.h...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=public-semweb-lifesci@w3.org;X-NUM-GUESTS=0:mailto:public-semweb-li
 fe...@w3.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dbcatalog;X-NUM-GUESTS=0:mailto:dbcata...@googlegroups.com
CREATED:20110108T145954Z
DESCRIPTION:This meeting will be held using fuze: please join at **Michel w
 ill send fuzebox info**\n\nNote: There have been various small hiccups with
  fuzebox so I recommend that you join ahead of time if you aren't sure abou
 t fuzebox working properly. I recently discovered that you will get *no mes
 sage* if there is no Internet connectivity - it will simply do nothing when
  you start the local fuzebox client.\n\nDuration: ~1 hour\n(Variable) frequ
 ency: ~weekly\nConvener: M. Scott Marshall\n\nSession Theme: Metadata for d
 ata discovery and dataset description using SPARQL\n\n* a model for provena
 nce\, versioning\, format and availability - Michel\, Alasdair\n  Relevant 
 docs:\n  the abstraction\n  - https://docs.google.com/drawings/d/1e6qsxPkc-
 qKecVTJGJePE1Nuy2sD8Puu-FsEtUtGC-o/edit?disco=AAAAAFWHcnw\n  sample impleme
 ntation using chembl: \n  - https://docs.google.com/file/d/0B4y0zfdRviKsS1l
 2NEttN3pfc1k/edit\n* Remaining metadata attributes in working draft - All (
 time allowing)\n   - Working draft:\n   - https://docs.google.com/spreadshe
 et/ccc?key=0Aoy0zfdRviKsdFJWTDFpblNXc3BtelhrdEpNYTdvbXc#gid=1\n* AOB\n\n***
 *******************************************************************\n\nMich
 el and Alasdair have model proposal for a dataset version and formatting: t
 hrashing out\nthe final details and will present as the first item at the n
 ext call.\n\nFocus on provenance and origin:\n\nVersion: literal\nDates: Fu
 ll date time with timezone\nModified by: URI for a person\nSource: Needs to
  be present and specify the version/date of the source\nPrior version: poin
 t to URI\nSuperseding version: Maintenance issue\; can be inferred\; proven
 ance vocabularies\nonly point backwards\nSubset/superset: only assert that 
 you are a subset of another one\nFrequency of change: estimate\; use a URI 
 for the value\, e.g. dublin core\nLatency of change: time it takes for chan
 ges in the raw data to appear in the derived\ndataset. Very specialised and
  probably not to be included\ncreated with: realised we need to point to a 
 tool that was used to generate the dataset\;\nparticularly for D2R or Bio2R
 DF point to versions of scripts\n\nAggregation of datasets is covered by so
 urce/derivation: simply include multiple sources\n\nAvailability\n\nAvailab
 ility: raises a maintenance issue\; could capture available until X if it i
 s known that\nit is no longer going to be available. Good for registry use 
 case\, but not necessarily for\ndata publishing. It is a monitoring propert
 y.\nPublisher: need to decide a value set: literal/URI\nFormat: mime type o
 f the file\, not the vocabularies used\; EDAM\, biosharing as\ncandidates\n
 data item HTML template: to automate access\nRDF dump: available in multipl
 e formats\nSPARQL endpoint\nAPI: point to a top level page about the API ra
 ther than each individual method\nCatlog/registry: point to records in regi
 stries. Inverse relationship with the registries\n\nView your event at http
 ://www.google.com/calendar/event?action=VIEW&eid=cm1yMWZub29jN2Q4NjdqaTdkZm
 dma2RkOGMgcHVibGljLXNlbXdlYi1saWZlc2NpQHczLm9yZw&tok=MTcjdzMuaGNsc0BnbWFpbC
 5jb20zYjk2YjBjYjkyNGM0Zjg2MTZkYjJkZjZkMjg2Nzk1MTA4YTE0NmQw&ctz=America/New_
 York&hl=en.
LAST-MODIFIED:20130429T123739Z
LOCATION:#hcls
SEQUENCE:5
STATUS:CONFIRMED
SUMMARY:Linked Life Data
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:EMAIL
DESCRIPTION:This is an event reminder
SUMMARY:Alarm notification
ATTENDEE:mailto:public-semweb-lifesci@w3.org
TRIGGER:-P0DT1H0M0S
END:VALARM
BEGIN:VALARM
ACTION:EMAIL
DESCRIPTION:This is an event reminder
SUMMARY:Alarm notification
ATTENDEE:mailto:public-semweb-lifesci@w3.org
TRIGGER:-P1D
END:VALARM
END:VEVENT
END:VCALENDAR

Attachment: invite.ics
Description: application/ics



Reply via email to