katya: Will discuss what we're
doing. Started project 2.5 years ago, continuing until the end
of this year.
... Some of our approaches are more generally applicable than
only IOT.
... Multiple platforms, using different stnadards.
... Semantics of data differ. Problems accessing them and
exchanging data.
... Two use cases: Transport and logistics; and
eHealth/mHealth
... We approach interoperability at all levels.
... On data and semantics layer, we have a component:
Inter-platform semantic mediator (IPSM)
... Transforms RDF graphs. Based on translation channels --
pub/sub paradigm
... Preliminary "lifting" step are done by producer and
consumer.
... We align to/from central ontology.
... We assume central ontology to be used. Generic Ont of IOT
Platforms, used for central ont in IOT domain.
... Has basic concepts limited to general IOT concepts.
... Estension of Generic Ont for IOT platform (GOIoTPex) for
each domain, such as healthcare.
... Central ont was designed to be extended.
... Core concepts include User, Service, Platform, Device,
Location, Unit, Observation
... Inter-Platform Semantic Mediator is not restricted to
IOT.
... It's a universal RDF translator / graph rewriter.
... Configurable with alignment files. Main use case is for
translating small messages.
eric: Can we see the mapping files?
katya: Yes, in a moment.
(katya dropped off -- lost connection?)
(pawell takes over with an older version of the slides)
(katya is back)
katya: we only translate when needed
(skipping to example)
pawel: Alignment API, file is in
XML.
... Level 2 is mapping of complex expressions, which we
do.
... source and target RDF patterns show what you want your
graph to match, and its
... rewritten into the other.
... Patterns are similar to RDF but they have variables.
katya: considering FHIR ont for use.
pawel: you provide Config files /
alignment files only for translations you actually need.
... For example, a module for eHealth domain.
... BodyCloud is from one of our partners, a medical platform.
It sends observations, using mobile device as
intermediary.
... E.G., CTX is an owl individual, a BodyClouid object.
Describes an observation about blood pressure.
... WE have generic observation in central ont, but not
BP.
... We rewrite RDF graphs configured by alignment files, that
expand the model in which the same info is expressed.
katya: In alignment format, it is quite expressive.
<scribe> ACTION: Katya to send slides
<trackbot> Sorry, but no Tracker is associated with this channel.
(Ran out of time. Scheduled followup for Apr 13, 9am Boston time)
ADJOURNED
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/Present: Pawel, EricP, Katya, Joao/EricP, Paweł Szmeja, Katarzyna.Wasielewska (katya), / Succeeded: s/EricP, Paweł/Present: EricP, Paweł/ Succeeded: s/EricP, Paweł/Present: EricP, Paweł/ Succeeded: s/Present: // Present: EricP Paweł_Szmeja Katarzyna.Wasielewska_(katya) David_Booth Harold_Solbrig No ScribeNick specified. Guessing ScribeNick: dbooth Inferring Scribes: dbooth WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: katya WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]