Specification

• 4.1.1 Should the "timegate" link only be present when an object is versioned or should all LDPR that could be versioned provide this link?
  • Yes, it should always be present
• 4.1.2 The Fcrepo spec doesn't mention it directly, but is there a conflict between the Memento "Content-Location" header and External File's "Content-Location"?  Can they both appear in the same response?
• 4.1.3.1 In supporting PUT to LDPRv, which would cause an LDPRm to be created, is this just in support of server managed versions?  Or is PUT to an LDPRv intended to be addressable separately from a LDPR so as to trigger this behavior?
• 4.3.1 How do you determine what serializations are available for TimeMaps?  HEAD is not currently supported and is not in the Memento spec.
• 4.3.1 Why does each memento need a separate TimeMap to be created, rather than sharing one for all of the LDPRv and LDPRm of one LDPR?
  • In the modeshape implementation, the timemap is the fcr:versions endpoint?
• 4.3.1 LDPCv must not be contained by the LDPRv
  • does that mean that fcr:versions will no longer be a subpath of the LDPR?
  • This only applies to ldp:contains, the uri is irrelevant
    
• 4.3.5 What is the expected behavior if a POST to an LDPCv is made which specifies a Memento-Datetime which is already in use by an existing LDPRm for that LDPRv?
  
  • Having two memento's with the same datetime would result in datetime negotiation yielding indeterminate results.  
  • Ignore request and return a 412 response?  Delete and replace the existing version?

Delta

• 4.1.1 Add HTTP header Link: rel="timegate" referencing itself
  • versions will need to be accessible via the TimeGate, which is the LDPRv, versus TimeMap (which is what '/path/to/object/fcr:versions' currently is).  New URL for TimeGate access to versions?  Actually, a URL with fcr:versions in it could probably be returned, so long as negotiation on what the DateTime the user wants happens via the TimeGate, which is the LDPRv itself. 
• 4.1.2.1 include 'Vary: Accept-Datetime' header in response
• 4.2.3 When requesting a Memento or a TimeGate, a Link header must be returned with type of "original" which points to the URI of the original.  See 2.2.1. Link Relation Type "original"
• 4.2.3 "Memento-Datetime" should be returned when making a GET against a memento, indicating the timestamp of the memento
• 4.1.2.2 The TimeMap link may support "from" and "until" attributes, do we want to provide/support these?  See 2.2.3. Link Relation Type "timemap"
• 4.1.2.1 How is fedora going to handle Accept-Datetime negotiation?  nearest version?  nearest version before requested time?  Or is it even going to be used this way?  See 3.1. Datetime Negotiation (first paragraph after example steps)
• 4.3.5 Are we going to need to take away the ability to provide version labels since they are not a part of the Memento API and not mentioned in the fcrepo spec?
• It would be helpful to record which Datetime Negotiation pattern the modeshape implementation uses in documentation