Page tree
Skip to end of metadata
Go to start of metadata

Time/Place

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

Attendees 

Agenda

  1. Kevin Ford's issue from list

  2. Implications of blank node redesign:  FCREPO-2108 - Getting issue details... STATUS

    1. Based on community input 4.7.3 is reasonable
    2. Need upgrade utility:  FCREPO-2423 - Getting issue details... STATUS
  3. Potential 4.7.3 release

     Click here to expand...

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due
    Loading...
    Refresh

  4. Benjamin Armintor: Input re:external-content from LDCX
  5. ...
  6. Status of "in-flight" tickets

      Click here to expand...

Ticket Summaries

  1. Please squash a bug!

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

  2. Tickets resolved this week:

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

  3. Tickets created this week:

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

Minutes

Kevin Ford's Issue on the List

Traversing the repository looking for corrupted resources won't work because the ldp:contains predicate is not set for the corrupted resource.

500's were received during the long-running ingest which led to this discovery.

Possibly a concurrency issue, which could be eliminated as a cause if there was more information available.

Unfortunately no TRACE level logging available, nor stack traces from the logs for a root cause.


Would be good to see if it's possible to do an import/export at the ModeShape layer to see if ModeShape can read the corrupt resources.

Mike Durbin thinks it is possible to provide a patched Fedora to ameliorate the issue if we can isolate where the issue is occurring.

Possible release for skolemizing blank nodes

All resolved issues resolved in the master branch are non-breaking and could be rolled into a minor release.

Although not strictly required, those with existing blank nodes that plan on ingesting new ones, you'd have both hash uris and .well-knowns.

Tenative +1 to get those changes out and go through the process of community testing.

The new Jena library changes some xsd info that could cause some existing clients to break without a small configuration change.

Simeon Warner suggested using configuration to enable new blank node behavior, but to leave it disable by default.  Then it's DEFINITELY non-breaking, as opposed to possibly non-breaking.

  • No labels