31 Jul 2018


Pawel, Kasia, EricP, David_Booth, Glenna_Mayo, Harold_Solbrig
David Booth


Blood pressure translation example in IPSM

<inserted> Files for today's demo from Pawel: https://lists.w3.org/Archives/Public/www-archive/2018Jul/0008.html

pawel: We set out to do the Blood Pressure example from EricP in IPSM.
... We started with the same Turtle input, but put it into JSON-LD and added a metadata section, which is not used for translation.
... The <filters> says what must be the datatype of that data. If it is not specified, then any datatype will be accepted.
... Another difference is that anything that is not explicitly translated in IPSM is passed through unchanged. WHereas in shex anything that is not translated is lost.
... within a single cell you cannot have optional values. But you can have one cell with the value and one without.
... Also, we have the RDF/XML for the whole alignment, but we also use Turtle. But there was a problem with writing <http:...> absolute URIs in the RDF/XML. So we used prefixed names in Turtle.
... Also we don't have a focus node. But we could instead use an absolute URI (as a prefixed name).
... A side effect is that if we use URI here we have to repeat the same URI in the output, or it would be written over.

eric: If you recognize a triple pattern, it will behave the same way?

pawel: Yes. We treat it the same as anything that does not match.
... We are doing this (adding the data) because the data is typically polluted with annotations from others, but only a part should be translated.
... To connect to a sys, you write a module for you sys.

david: I like that idea of passing through anything that is not recognized.
... you use named graphs for metadata vs payload. Did you consider using a separate graph for the translated result?

pawel: We considered it, but could not reach consensus. Also considered other graphs for more things.
... But we left it this way for performance.
... These examples plus our observations should be enough for an article.
... I can start a repository for us to collaborate on writing the paper.

Next meeting

harold: I'll be out on vacation next week.

eric: I will be away on vac until Aug 27.

AGREED: Next meeting will be Aug 28.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/07/31 16:40:09 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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: i/pawel: We set out/Files for today's demo from Pawel: https://lists.w3.org/Archives/Public/www-archive/2018Jul/0008.html
Present: Pawel Kasia EricP David_Booth Glenna_Mayo 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: 

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]