search

sul-dlss-deprecated / taco

Apache License 2.0
10 stars 7 forks source link

Fedora 4 API comparison to TACO #126

Closed cmharlow closed 6 years ago

cmharlow commented 6 years ago

Tom request for Christina

jcoyne commented 6 years ago

I think this is true of the API regardless of what implementation

  1. Fedora API is incomplete. Still unclear about the expectations for Fixity and Notifications.
  2. Can't handle ordered lists (which can be worked around, but hurts performance)
  3. No query or constraint support which is important for our use case where we don't allow duplicate SourceIDs.
  4. Resource permissions as resource properties vs WebACL which is slower because it requires multiple requests.
  5. TACO semantically validates data, Fedora 4 does not.
  6. Fedora API is very complex because it encompasses the LDP spec and the WebACL specs, both of which are complex.
  7. Fedora API has complexity to support every possible data shape, vs TACO supports only our SDR data shapes.

And this is true of all implementations that I know of (maybe not A Colburn's?):

  1. Centralized vs. Distributed (which goes to performance and scale requirements)
cmharlow commented 6 years ago

Scheduled meeting for this. Need to make prep materials and confirm Tom will actually show up.

cmharlow commented 6 years ago

Invite Stu.