May 11, 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

• Nick Ruest
• Melissa Anez 🌟
• Bryan Brown
• Don Richards
• Jared Whiklo
• Diego Pino
• Christina Harlow
• Ed Fugikawa

Agenda

1. Discuss: rdf namespaces and properties: dc, dcterms, schema.org and DPLA alignment

• http://ldcx2016.sched.org/event/6Ws7/11a-edm-dpla-map-pcdm-iiif-alignment

2. #182

• Proposal
  • Crayfish: https://github.com/ruebot/crayfish
  • Next steps?
    • Merge existing pull requests?
    • Close pull requests, and re-do them on new repo(s)?
    • Consensus on "Crayfish"?
      • We need an adorable logo from Melissa, right?
    • Finalize "Camel" name

3. May Sprint, 16th-27th

• Priorities
  • #182
  • Microservices
  • Sprint milestone tickets
• Sign-up sheet

4. ... (feel free to add agenda items)

Minutes

1. Data modelling. Lots of different options. How to reconcile. This conversation started before LDCX, where Nick and Christina were in a group that also discussed the topic. Time to talk it out amongst the people of CLAW.

Diego: We've been working with PCDM for a while now. We've had some discussion about how close we can match our idea of what we need to PCDM, and if it really works for us. This is related to how much alignment really matters to PCDM> If we're going to RDF/linked-data road, not only is modelling a concern, but making our data understandable to other system. Also, making the way we display our assets as close as possible to the model. So IIF comes in there. For instance: ordering in PCDM is different from IIF, which uses JSON. Much simpler to manage. Major concern right now is finding the best approach. Glad to have Christina here, since she has a lot of expertise on this.

Christina: LDCX session is linked in the agenda. Within that session you see detailed descriptions and diagrams, which link to a spreadsheet she started before LDCX. Omits IIF, which she is aware of but not involved in. This gives us a place to start. You can see where people have started to use PCDM, now PCDMworks in the Hydra world. Some parts of PCDMworks will be integrated into PCDM. Not sure what the governance model is for PCDM. Or how these choices will be made.

Nick: There are a set of Committers, so if a PR is proposed it goes through review by them, such as here.

Christina: Time to get rid of the concept of "work" from Hydraworks because it's not being used for anything special. Work may be on its way out. Curious how we get all the descriptive metadata from all the various parts of the models. How to link PCDM objects to other domain models? Bibframe, etc? Rob Sanderson proposed pulling something from Europeana. They make more of a split between web resources and source resources. Are there questions for CLAW implementation of PCDM? Will you use some extension like Hydraworks?

Nick: A few weeks ago we were worried we weren't quite understanding what was going on with PCDMworks and making sure that both communities implement PCDM in a consistent manner so we keep the dream of interoperability alive. We're still trying to get to the point where we actually implement. We've done a little with PCDM Collections, but otherwise it's a lot of models and ideas.

Diego: Right now PCDM behaves more like a vocabulary than a real ontology.

3. Sprint: Next sprint runs May 16 - 27. Priorities: Restructuring and continued work on microservices. Check out milestone tickets.