Handling of Fedora Blank Nodes - Major or Minor

42 views
Skip to first unread message

Andrew Woods

unread,
Apr 13, 2017, 2:18:42 PM4/13/17
to fedor...@googlegroups.com
Hello All,
For those of you who follow commits to the Fedora core code base, you may have seen the recent improvement to how blank nodes are handled (thank you, Esmé).
https://jira.duraspace.org/browse/FCREPO-2108

The summary is that when a Fedora resource is created with RDF that contains blank nodes, instead of those blank nodes being created under the ".well-known/" area of the repository, this commit changes the behavior to now create the blank nodes as hash-URIs under the Fedora resource, itself.

This is an important improvement, and one which we would like to get out to the community... but we also want to respect the commitment of limiting the number of "major releases" of Fedora to one per year. 

Although this update does not represent a major release in the sense that neither the API is changing nor is a backend storage migration required, the interaction model from the client perspective may potentially be affected, depending on current clients' expectations around interacting with Fedora blank nodes.

Your input would be helpful in considering whether to release this update as a minor release (4.8.0) or not.

Please add your thoughts to the following GitHub issue detailing:
- whether or not this change is a feature that is of interest to you, and
- whether your client application would consider this change a major or minor update.
https://github.com/fcrepo4/fcrepo4/issues/1188

Thanks in advance,
Andrew
Reply all
Reply to author
Forward
0 new messages