Time/Place

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

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

Attendees 

• Unknown User (acoburn)
• Bethany Seeger 
• Jared Whiklo
• Yinlin Chen
• Esmé Cowles
• Aaron Birkland
• A. Soroka

Agenda

1. Reconsidering hash URIs

   1. see  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Ticket Summaries

1. Please squash a bug!

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

2. Tickets resolved this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

3. Tickets created this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Minutes

Discussion on Hash URIs and how they are created/stored/managed in Fedora 4 and what their life cycle should be like.  

Unable to locate Jira server for this macro. It may be due to Application Link configuration. - The bug is not a big deal by itself. User noticed that you can't delete them because the server managed triples hang around. Via a Sparql updates you get errors. Via Httpd delete - you end up deleting parent.  

Hash URIs are a good alternative to blank nodes. The current implementation is not inline with semantics used on the web.   They get their own container and server managed triples, which is not what people generally expect.

People shouldn’t link to hash URIs outside of their repo, but we can’t prevent them from doing that.

Should we only allow a link from parent to the hash URI?  One can make a link from hash URI to anything else.

If we did this the OAI people would need to do something different - maybe in the API extension architecture. 

We should do some research to see who is using hash URIs now and their use cases. 

Proposal:

• Accept and follow fragment semantics in Fedora 4,
• Introduce scoping mechanism for hash URIs 
• Suppress the server managed triples on the fragments.

Esme will file a few tickets on these and then email the fedora list to gather any community input that people have to offer.

Notice:  The API Extension meeting scheduled for tomorrow is cancelled as most of the regular attendees are unavailable. It's been moved to Oct. 30th 2pm EDT.