...

Attendees 

• Unknown User (acoburn) 
• Bethany Seeger 
• Jared Whiklo
• Yinlin Chen
• Esmé Cowles
• Doron Shalvi
• Unknown User (daniel-dgi)
• Andy Wagner

Agenda

1. ...

• Aaron Birkland
• A. Soroka

Agenda

1. Reconsidering hash URIs

   1. see 

      Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1764

Ticket Summaries

1. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

2. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

3. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

Minutes

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

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.