IPSM Example files

Kasia sent them to us in email on May 14.

pawel: The JSON files (JSONLD) have more than one graph inside
... Decided to use JSON-LD because a lot of developers know JSON, and it fits our semantic approach.
... Shex looks like a very nice tool. Q about different representations of the output.
... Are different forms of output supported by different libraries?

eric: Yes. Re standardization, the result format is standard. Proof of validity is not standard, but two or maybe three implementations support it, so perhaps it is a de facto standard.

Example files: https://lists.w3.org/Archives/Public/www-archive/2018May/0003.html

(pawel demonstrates IPSM translator)

pawel: Previously we were using XML (not std RDF/XML), but now we are using std RDF/XML. The example that Kasia sent is the old version.
... Looked at an alignment API: http://alignapi.gforge.inria.fr/
... Alignment API defines different levels of alignment.
... Level 0 of alignment allows mapping class names.
... Uses ODOAL classes. Not well documented.
... Decided not to use it. Used our own.
... <entity1> and <entity2> tags contain different graphs.
... Variable CTX, rdf:type sosa:Observation
... <entity1> is what is deleted, <entity2> is what is inserted.
... Other types (outside of <entity1> and <entity2>) give more capabilities. E.g., you can specify a variable as a datatype.
... There are also filters.
... <transformation>s are functions. We don't have documentation on it, but it's quite complicated.
... Parameters are in order, function name, and return type, and variable name for receiving the result.
... You can also define your own functions, but need to plug in your own jar.

eric: Did you consider using SPIN?

pawel: Did not consider it.
... Core functionality seems very similar to ShExMap, but ShExMap has more emphasis on verification.

ADJOURNED