RDFS/OWL Team

RDFS Call
Kelly, Joachim, Deirdre, Guillaume, Eric

Browser interface mission - to make it less 'custom', modularizing the code into pieces that are not DDI specific, but are libraries.

XMI - UML - RDF Schema - ShEx and OWL representation

Diagnostic functionality with the intention to show what the unresolved things are and to figure out what should be in the View.

If the property value is not defined in the view - Suggestion to grey it out and say they are intentionally not in this view, but available in the full ontology.

What will be published in the prototype:

OWL Ontology for all of DDI (DDI_4-DRO.2-OWL.xml)
Views as separate Ontologies - JSON, OWL, ShEx available as files in github
Visual Representation (Eric's ShEx Browser) - almost finished - remove the W3C branding, etc.
Lode - Common tool for visual representation of OWL. Currently not working.

BUG

ObjectProperty - ddi:contains?

Eric will troubleshoot.

Other
New canonical version to be produced by Achim next week or following week. The change will be the regular associations reversing order.

Send the links to the TC for the prototype. Kelly to communicate with Eric.

Will have first OWL representation ready for review by March 8th. Will take a look at that and then pass on to TC after next week's call.

Achim to work on rules based on the Dagstuhl documents.

Eric to write down rules of what he has done thus far. 

Feb. 1, 2018

Attending: Kelly Chatain, Eric P., Achim

Timeline and how to support the iterative process.

• Generation of the vocabulary is the most important.
• Can we use the class documentation?
• Eric testing parsers for various languages. Should transformation work on current drupal?
  EA flavor XMI should be used.
• Targeting the obsolete EA right now. Doing the work that makes it easy to switch to canonical.

Iterative process:

• Achim on vacation Feb. 12-16th.
• Eric questions: abstract/interface - reserved names or problem with tool?
• Input: Are property names effectively globally unique? Eric can produce a list of properties that have the same names.

Action: Achim to write RDF Invite

Action: Create JIRA issue for modellers about global unique property names.

Action: Strategy template on wiki for RDFS (Kelly) 

Double check the rules review with Eric.

January 26, 2018

Attending: Kelly Chatain, Eric Prud'hommeaux, Achim Wackerow, Jared Lyle

Logistics and Work Organization:

--Payment and support - Eric to submit the invoice to Jared on a monthly basis. Details are in the contract.

--Possible weekly call with following attendees: Achim, Eric, Kelly, Deirdre, Darren, Dan Smith, Guillaume, someone from modelling. Wendy or Dan Smith from the technical committee, specifically in regards to the production framework. 

--Set up an email list or group function with an archive function as a reference.

      Action: Kelly will look into JIRA options, eric will provide an example of a W3c mailing list?

-- Wiki: Kelly will set up a team page on the wiki, JIRA issue tracker, we need a bitbucket site for RDF work

Achim's list of issues outstanding in RDF work: (link to document)

--Reasonable chance that JSON LD will do what we need without too much effort.

--OWL binding/syntax – We are talking about the validation of the OWL model, then the examples.

--Validation in RDF, to make it falsifiable, we need to keep track of the things that can be disjoint which takes more effort. Syntactic validation is possible for the prototype (classname conflicts, etc.)

--Prioritizing issues for prototype and then parking the others.

--Documentation for validation needs to be in ‘english’ not computereese. In reStructuredText? Similar to markdown

--Re: Xslt to transform xml to rdf – would the xslt be a deliverable (user-friendly and tested)? Yes. All tools developed for our purposes should be part of the production framework, which will be published. The prod framework will be used by others to produce other bindings, or flavors of a binding. Should we use Javascript or scala or something else that is easier to read. Requires a different toolchain, but what is the most popular one?

      Action: Should be discussed in the RDF group and document discussion.

      Action: Any issues that we did not think about before, please document and specify the amount of effort needed for the prototype.

     Action: Who will debug and fix the xslt? – Oliver Hopt

--How can generic rules be used by a transforming tool so that the tool can be changed easily in the future. Can we do that currently for the prototype? Should we move away from xslt now or in the future? The cost is higher to carry it forward, so we should move (Eric) Transforming instance data to instance data is what more people do. Transforming the model is a smaller community. Eric is quick at the javascript.

     Action: Send Eric the latest version of the xml that Drupal spits out, the corresponding OWL, then the rules document (cygniak and Copenhagen)

--Are predicates unique across the system or within a particular class? We need to dive in a little more on this issue. If we had a converter, we could see when we were reusing predicates, then we would know how to make decision about migrating a few predicates or to say they effectively have the class implicitly prepended onto their name.

Example:

In one class is a person structure, but in another class is a string.

      Action: Kelly to confirm Eric JIRA permissions, bitbucket, etc. Will send emails to everyone.

Next call : Feb. 1st at 5pm CET with Achim, Eric,