March 2, 2016

Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join. Here is the info:

• Time: 1:00pm Eastern Daylight Time US (UTC-4)
• Dial-in Number: (641) 715-3570
  • Participant Code: 304589#
  • International numbers: Conference Call Information
  • Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
• IRC:
  • Join the #islandora chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #islandora on irc.freenode.net

Attendees

• Ed Fujikawa
• Melissa Anez
• Nick Ruest
• Diego Pino
• Daniel Lamb
• Ben Rosner
• Jared Whiklo 💥

Agenda

1. Sprint debrief

• https://github.com/Islandora-CLAW/CLAW/milestones/Community%20Sprint%20-%2004

2. March Sprint

• March 21 - April 1

3. CLAW Lessons
4. Project Planning
5. ... (feel free to add agenda items)

Minutes

1. Did not complete all our goals. Had 13, closed 5 and left 8 open. Some open PRs to discuss.

   Jared to test and merge PR 158.

   Nick to test PR 160, we will close PR 159.

   On chullo Danny closed PR 36, Jared to open a new one.

2. March sprint #5 - March 21st - April 1st

   Nick will be a LDCx in the first week.

   Danny may become a medical miracle during this sprint.

   Sign-up here : https://docs.google.com/spreadsheets/d/1hVeyoiSNNBk8RvtUAZxYQ57QURx89JFFzNey0yOUzcg/edit#gid=1348559236

   Move all open issues from sprint 4 to this sprint and not add new goals. Nick did the issue moving.

   Nick will be in and out this month, Danny will chair next week's call.

   Someone to chair CLAW call on March 16, 2016 and coordinate CLAW kick-off call with sprinters.

3. CLAW lessons

   A wonderful success, had 33 - 34 accounts connected. Many had more people sitting in behind those. Possibly over 50 participants.

   Continuing for another 8 weeks.

   Once the screencast is available it will be shared on the Islandora Youtube channel.

   Should the first lessons on adding items to Fedora 4 utilize PCDM objects.

   Why do we use PCDM?

   Compatibility with Hydra but also the existing Hydra-Works data model is the same as how Islandora was being designed.

   The ontology has no semantic requirements. If PCDM was more restrictive it could ensure it is actually inter-operable.

   Jared suggests forking https://github.com/duraspace/pcdm to Islandora-CLAW and make changes based on our use-cases in PCDM or extensions for specific content models (ie. Basic Image).

   Diego will make an issue and fork the PCDM github to allow us to make our changes.

   LDP is a tree-builder, so we still need to add additional semantics for our uses.

4. Project plan

   Diego, Danny & Melissa has some discussions on this. Has there been any movement on this?

   Danny : Each service is a discreet chunk that can be worked on for funding calls?

   Nick : Project plan and a diagram. We have trouble because we don't fully understand the full context of the stack. Perhaps for the April sprint we can have a look at it. Do not create a diagram of the stack until Nigel's work is merged in and the PHP/Silex microservices are merged into the main codebase.

   Ed : I don't need something now, and am interested to see how the classes go over the next couple of weeks.

   Ben : I agree with Ed.

5. Misc

   Danny : Do you think EasyRdf is any good. irc log @ 12:17

   Diego : I use Grafitti (sp?), but not built for use inside of a Silex app because of namespacing. It is over complicated and too restrictive for what we need to do. But it is what we have. We are not doing big RDF building and traversing.

   Danny : I agree it is what we have. If I side-stepped the whole thing and parsed the graph and just called toRdfPHP() on that it returns an associative array.

   Diego : My fear is that if the package maintainer wants to change some functionality then it could break. The other way is to transform everything to JSON-LD and the use JSON-LD libraries. JSON-LD implementation in PHP is pretty stable. If we can work on our side with only JSON-LD. Also might have with non-SQL databases.

   Danny : What has prompted this is instead of mindlessly copy-paste. That I understand what Diego did and why he did it.

   Diego : Namespacing is not handled well in EasyRdf either. It doesn't remember it so you could end up with duplicated ontologies.

   Danny : Do we restrict input to JSON-LD

   Diego : I am okay with that

   Jared : I am not okay with that, mostly I find that too restrictive.

   Diego : So maybe we accept anything that EasyRdf accepts and convert it to JSON-LD for behind the scenes.

   Diego : A JSON-LD parser from DigitalBazaar handles RDF to JSON-LD transformation. More people are supporting JSON-LD than RDF, so if we can convert RDF to a good JSON-LD document than we are fine.

   Danny : I will continue using EasyRdf for now.