Spec defines minimal but required set of capabilities that must be impl=
emented in order to =E2=80=9Cdo Fedora=E2=80=9D
There are a range of capabilities, and you may or may not do all of the=
m=20
If you do any of them, here is some guidance/expectations on the behavi=
our
Josh: what is the scope of the spec?=20
Is the spec mainly about aligning Fedora with LDP, or should it also in=
clude things (like fixity) that are historically associated with Fedora tha=
t do not fit into an HTTP interaction model?
Josh: It's an important function of this k=
ind of system, and the expectations about how it might be done need to be c=
lear
Danny: some discussion of back-fillability of functions
Aaron: application concerns are different for RW apps than for RO apps,=
too
Andrew: consider the notion of substitutable backends- seems like spec =
should be clear enough that an app should be able to be agnostic to some ex=
tent; what capabilities should be guaranteed? what are implementation depen=
dent? is a key distinction for the API definition effort. What can we do?=
li>
Aaron: unsure how much we can do with regard to, for example, the flexi=
bility in the LDP approach of constraints documents and statement rejection=
(again mattering to RW and not to RO apps)
Andrew: To what degree is substitutability reasonable or sensible?
Nick: If we're silent on SSR, cannot promise any functional substitutab=
ility (in managing apps)
Danny: the spec is really leading me to use the simplest interaction mo=
dels, which might good, but may also be too simple
Josh: feels strongly that it should be a refinement of LDP
Kevin: If the purpose is interoperability with an eye toward swapping o=
ut back-ends then we should tighten the spec
Pain point: putting RDF (e.g. an ontology) into Fedora that does not co=
nform to Fedora=E2=80=99s restrictions (e.g. single subject rule) so it mus=
t be uploaded as a binary file
Is the SSR a technical limitation or an important part of what Fedora i=
s?
Andrew: it is a philosophical limitation - Fedora is a digital object r=
epository so RDF describes objects in Fedora rather than random subjects in=
the world
Basing this on mailing list feedback is not necessarily indicativ=
e of what people are doing
Jared: Do we define breaking change based on the repository or potentia=
l workflows?
We should produce a tool to remediate the different ways of handling bl=
ank nodes and put out a minor release: Unable to locate Jira server for this macro. It may b=
e due to Application Link configuration.
Suggestions from recent Fedora Leaders meetings=20
Have an elected Fedora Committer join Fedora Leaders calls
Have DuraSpace-hosted release testing infrastructure
Interest in tighter alignment of effort and priorities between Islandor=
a/Hydra/Fedora