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)
- U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
- International toll free: http://www.readytalk.com/intl
- Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial-in number
- Once on the call, enter participant code 2257295
- IRC:
- Join the #duraspace-ff chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #duraspace-ff on irc.freenode.net
Attendees
- Osman Din
- Kevin S. Clarke
- Longshou Situ
- Unknown User (escowles@ucsd.edu)
- Ralf Claussnitzer
- Unknown User (acoburn)
- Michael Durbin
- Ed Fugikawa
- Yinlin Chen
- Greg Jansen
- Stefano Cossu
- Nikhil Trivedi
- (others who plan to attend, feel free to add your names in advance)
Agenda
- ACL discussions from HydraConnect
- Moving towards 4.0 release
Minutes
- ACL in HydraConnect
- Esme: Hydra wants to have standard Fedora 4 ACL system, would like feedback from Islandora/other users
- Two approaches: one is like Fedora ACL & Hydra schema, other is emerging W3C spec, but not fully baked yet
- Aaron: different approaches: predicates on objects declaring access, or external objects referring to objects and policies
- Esme: Hydra wants to have standard Fedora 4 ACL system, would like feedback from Islandora/other users
- Moving towards 4.0 release
- Esme:
- Many features that are not ready for production and should be removed to separate branches or modules.
- See 2014-10-08 - Fedora Technical Working Group
- Stefano: add Node type to the list
- Esme:
- Nikhil: Database connector
- Modeshape classes aren't readily extendable, talking to Modeshape developers to make that easier
- This would be Mode 4.1, so Fedora 4.1 or later
- Stefano: Mike brought up ordered lists - want to be able to order child nodes in some cases
- Considering MPTT modified-preorder-tree-traversal
- Esme: In Hydra RDF, we've used rdf:List, and talked about the ordered list ontology (which seems like a nicer solution)
- Greg: Ordering harder to validate the structure
- Mike: maybe we could convert these to ordered nodes in Modeshape?
- Esme: this common use case, so it could be a good feature, but it could have performance implications
- Greg: are they fixing the modeshape performance for many children?
- Esme: they are working on it, not sure if it is fixed or if it can be
- Stefano: internal sparql query: didn't seem to work, what's the status of this?
- Longshou: can only query properties that are persisted in Modeshape
- Stefano: want to have real-time access, access to stuff that's not indexed.
6 Comments
Stefano Cossu
Unknown User (escowles@ucsd.edu): I agree that Ordered List Ontologies are more straightforward to implement and probably more efficient then MPTT/Nested Sets. How do we go about using blank nodes in a Fedora OLO? In the examples provided, the predicate of a olo:slot is a BNode.
Unknown User (escowles@ucsd.edu)
You should be able to use blank nodes – they will get Skolemized into URIs that start with /.genid/well-known/. Though if you want to avoid blank nodes completely, I think you could just create child nodes of the object in question instead.
Stefano Cossu
I raised the question about BNodes a couple of committer meetings ago. See my comment: Re: 2014-10-02 - Fedora Committer Meeting
Stefano Cossu
Basically my problem is that I don't know how to relate the BNode to the original triple it was constructed in.
Unknown User (escowles@ucsd.edu)
If you PUT that same RDF, the link to the blank node is created, but when you use SPARQL Update, some internal identifier is used as a string for some reason. I've filed a bug for this: https://www.pivotaltracker.com/story/show/80483482
Stefano Cossu
Longshou Situ: added ticket for sparql query on non-persisted nodes: https://www.pivotaltracker.com/story/show/80389314