Open edsu opened 5 years ago
Dunno. That seems like a reasonable plan. The latest polished version wasn't under our control, actually, and is purported to be at https://www.rfc-editor.org/authors/rfc8493.xml .
Oops. That link's now broken. I've sent an email to the RFC-editor asking where we can find it.
I was thinking this GitHub repository would still be useful to use for people who have implementation questions about the specification. Having a current version of the spec in here would be handy for that? Or were you thinking another communication channel would work better?
I think we should update this so we can start on the 2.0 .bagit version
If it works better for all concerned to have the repo live at @libraryofcongress that would be fine too. I would just like to see development happening on Github as much as possible, since I know there are people who would like to join the conversation about how to implement 1.0 and also help work on enhancements. GitHub still seems like a good place for this to happen?
@acdha I think you should now have the latest XML file in your email. I suppose it should be reconciled with the last few tweaks that RFC Editor made to the TXT file that didn't make it into the XML file.
I believe related to this issue; should the purl link -- http://purl.org/net/bagit -- point to https://tools.ietf.org/html/rfc8493, instead of https://tools.ietf.org/html/draft-kunze-bagit-17?
I don't see why not. (I didn't know there was such a purl)
As of https://github.com/LibraryOfCongress/bagit-spec/commit/753a54db89bc312998c503c9a0048629ad30a219 the XML file as received from the IETF is now in the master branch of the Library of Congress repository.
Great, so I guess that's where discussion should happen? Can the LC repository be made into the master repo?
Congrats on RFC 8493! Is the plan to put the lastest spec test in this repository or over at https://github.com/libraryofcongress/bagit-spec ?