Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PairTree reference #414

Closed
pwinckles opened this issue Dec 12, 2019 · 4 comments
Closed

PairTree reference #414

pwinckles opened this issue Dec 12, 2019 · 4 comments
Milestone

Comments

@pwinckles
Copy link

I'm curious about the spec's reference(s) to PairTree. As far as I can tell, this is the most recent version of the PairTree spec: https://tools.ietf.org/html/draft-kunze-pairtree-01. It is a draft that hasn't been updated since 2009 and explicitly states the following at the top:

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

I guess it doesn't matter as much for the implementation notes, but it seems out of place to cite it in the OCFL specification.

@ahankinson
Copy link
Contributor

PairTree is implemented in a number of production systems and is widely known, so I think it makes sense to acknowledge it as a thing that is widely used, despite the notice.

Unless there is a better reference for PairTree that we missed?

@pwinckles
Copy link
Author

Not that I have been able to find. I don't know the history of it, so I've always found the PairTree situation odd. That is to say, odd that it would be widely used (is it?) but be unfinished and feature a number of undesirable performance characteristics.

@pwinckles
Copy link
Author

Feel free to close this. I was mostly just drawing attention note at the top of the PairTree draft.

@zimeon zimeon added this to the 1.0 milestone Jan 7, 2020
@zimeon
Copy link
Contributor

zimeon commented Jan 7, 2020

Editors agree that we can close this

@zimeon zimeon closed this as completed Jan 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants