What are our SMTs? What is the impact of allowing them to be modified?<=
/li>
What is an acceptable workflow for changing interaction models? Does th=
e presence of a matching rdf:type in the RDF matter?
What is an acceptable workflow for updating the properties of a resourc=
e?
What is an acceptable workflow for restoring a version? (either from a =
memento or from a local export)
Should GET ONLY return SMTs when specifically requested?=20
Essentially, reverse the current behavior by requiring an "include" hea=
der instead of an "omit"
Should PreferContainment header be considered a subset of SMTs i.e. sho=
uld they be suppressed on omit SMT? (Not relevant if we going to reverse th=
e current behavior?)
Shall we make all resources versionable by default?
Follow-on question: Should it be possible to make resources non-v=
ersionable? In other words, are we saying, everything is versionable,=
period?
Implications: =20
Remove DELETE LDPCv
Remove "Enable Versioning" from HTML UI
<your agenda item here>
Please squash a bug!
key
summary
type
created
updated
due
assignee
reporter
priority
status
resolution
Unable to locate J=
ira server for this macro. It may be due to Application Link configuration.=
Tickets resolved this week:
key
summary
type
created
updated
due
assignee
reporter
priority
status
resolution
Unable to locate J=
ira server for this macro. It may be due to Application Link configuration.=
Tickets created this week:
key
summary
type
created
updated
due
assignee
reporter
priority
status
resolution
Unable to locate J=
ira server for this macro. It may be due to Application Link configuration.=
Properly suppressing Server Managed Triples, how do we deal with ldp:co=
ntains.=20
Meta-conversation about what are Fedora's SMTs and the workflow.
Updating a properties of a resource requires a special header to GET an=
d to PUT. Do we reverse the behaviour and get back the non-SMTs by default.=
But you are lacking some of the useful triples (lastModified).
We expect that READ is a more common action than write.
ldp:contains should be a SMTs, which makes (for Jared) suppressing SMTs=
by default a less enjoyable process.
Having Fedora ignore SMTs included in a PUT does not seem to be a break=
ing change and could be done post-5.0.0 release.
Should be able to update SMTs if you need to.
How do you restore a Memento?=20
Currently need to GET a Memento, set Fedora to relaxed mode, then resta=
rt and PUT with Prefer: handling=3Dlenient; received=3Dminimal
Need to have relaxed mode on a per-request
Is this an authZ question? Should only certain people be able to restor=
e versions?
What is the result of a restore? Do you get all the previous triples wh=
ether they are SMTs or not? That seems to be the consensus.
Consensus is to use a new Prefer header to allow per request overwritin=
g the entire resource including any SMTs.
Will restoring a Memento result in restoring an older ACL? Consensus is=
NO, the Memento is separate. The link to the ACL is a static link added by=
the server and because the resource is not removed/re-added the current AC=
L will remain.
Discussion to occur in Slack
Changing interaction models?=20
Currently there is no way to change between interaction models.
Currently you can add types in the ldp: namespace, this should not be a=
llowed.
Make all resources versionable by default?=20
Yes. Danny to create a JIRA to enable versioning. Also create JIRA to t=
ag code that is used for enabling versioning for future review.
Reviewing list of SMTs that Ben created=20
Is the list full and complete?
What is the expected behaviour in interacting with SMTs.
"Anything that is created by the server" as the rule for SMTs?
Anything created by the server, where if they did not exist the interac=
tion would be indetermined.
Any triples added to the resource as they are being generated on reques=
t. `ldp:contains` and some fixity ones. Also with RDF serialization.
Also make sure that on the testing side we ensure the correct behaviour=
of SMTs.