Date

06 Jun 2017

Attendees

Agenda

1) Where we are on our road map.

2) Open Action Items

3) JIRA Issues Review - https://jira.edmcouncil.org/projects/RDFKIT/issues

4) Todays content discussion.

Fragments + Quads project

spec.... status

maturity

30 June Deliverables discussion

HTML (plan A and Plan B) Also EXCEL

UML + OWL (NoMagic status + content

5) For next week.

Proceedings:

2017 0606 FIBO FPT RDF ToolKit

Omar did what he wanted to do with the fragments server. Still some issues with pointing to the fragments server. JG will assist. Omar - it works! Need to check something with Momento. Need to point to FIBO, not just vocabulary .ttl.

DA: Maybe some more issues with the entire FIBO. Omar: yes.

JG: Do we even need StarDog? We can generate these fragments ourselves on spec. Omar: but StarDog has more capabilities for running queries. JG: But spec has all versions.

DA: We are now putting a triple into every onto file telling us maturity level. So to be able to only publish Pink=Production, took 2 minutes. Using GREPS now. Could the fragment server fix this?

Omar: possibly. Need to keep fragment server totally up to date to help DA. In the meantime, DA continues hack. DA: Doing this fast now. Need to switch from fast to smart.

Omar: This is possible. Omar: Can you publish something for me to use? DA: Yes, the little script that I wrote. Omar will look.

JG: StarDog would be useful if we had A Box data. Don't have that now. Therefore, not so useful now. Instead we could generate all of these files and we can guarantee that there will never be broken links. Omar: Happy to drop StarDog. Rather to put focus on script.

Jacobus: On a FIBO modern website, it could do the same as the fragment server. Client could generate an interesting web page from the fragment server. Based on user profile, we can generate what is appropriate.

Omar: There is an API platform using HYDRA that could generate such pages. API Platform CRUD-Generator. 2 JG: FIBO-INFRA has what Omar is showing on the screen. JG and Omar will work together on this.

ACTION: JG: Will commit what he has to GitHub this weekend and then others can use this.

ACTION: Omar will ask the Ghent people questions such as how to link and what links are allowed. How does this URL work?

Omar: 1) pick up artifacts from the Jenkins server - 1 week. 2) do something with the generator - 2 weeks. 3) do something with the publisher sooner. All contingent if we drop StarDog for now.. All agree to focus on spec....... for now.

This is called Linked Data Fragments Server

Omar: https://github.com/api-platform/generate-crud Nothing to do with N-Quads. DA: Can do quick and dirty N-QUADS for 30 June.

For HTML, this can be done quickly for 30 June.

No PDF for June 30. Put this on the roadmap.

Do we do CSV for import to Excel, or straight to Excel? Depends on workbook or single worksheet. TC: Multiline values also an issue.

DA: Maturity Levels - not multiple branches inside of GitHub. Have one branch and mark all with maturity levels. Taking all of maturity levels and marking into master. This will help people working off line knowing what to do. This will be in INFRA-175 . Zip part nearly done. Eventually what DA is doing now will merge into the FIBO maturity model. This will be part of the FIBO artifact oncology. Now all hard coded in BASH. Needs to be automated.

Decisions:

Action items

jacobus.geluk@gmail.com [X] Will commit what he has to GitHub this weekend and then others can use this
Omar Khan (Unlicensed) will ask the Ghent people questions such as how to link and what links are allowed. How does this URL work?
Omar Khan (Unlicensed) 1) pick up artifacts from the Jenkins server - 1 week. 2) do something with the generator - 2 weeks. 3) do something with the publisher sooner. All contingent if we drop StarDog for now. All agree to focus on spec....... for now.