...
Andrew: Last-Modified wasn't changing when IndirectContainers were creating new child links
- Esme: Also updating when inbound links were created (because we were creating reciprocal links)
- Action: Esme: add to the design page
- Experimenting with explicitly managing our own last-modified property, or not creating reciprocal links
- Jared: Would that work include the various last-modified properties in the design page?
- Esme: No, that would be another ticket and could be more involved.
- I'll push my branch up and update the relevant ticket so people could find the work if they had time to look at this
Hash fragments: review description
Andrew: We should more description of the intended behavior to drive the implementation discussion
- Aaron: Are we talking about a specification like a TCK would involve?
- Hash fragments are not repository resources
- They can have properties, updated with standard CRUD operations (POST, PUT, and PATCH)
- Their properties would be included with their parent resource's properties
- Any repository resource can link to hash fragments without restriction, or management by the repository (e.g. their base URI wouldn't necessarily be adjusted if the repository base URI was changed).
- Hash fragments are not repository resources
- Adam: hash fragments can be created anywhere using the standard CRUD operations
- Esme: there are some permutations of hash fragments as objects:
- existing in the base resource
- pointing to another repository resource that exists
- pointing to a repository resource that doesn't exist
- Esme: there is some tension between referential integrity enforcement (which we want in many cases), against supporting full-featured linking like we expect on the open web
- Aaron: some of the use cases might have contradictory demands
- Andrew: we should be aware of this possibility and try to prioritize use cases.
Tickets to be removed?
- Investigating alternative ISPN backends:
- Code4Lib Philly post-conference event?
- Next release?