I'm pretty sure I've never had a unique idea in my life :-) So I apologize if it sounded like I was laying claim to yours. I certainly remember memento tracer--I just didn't know if it will be expressed as small JavaScript plugins for different web archiving technologies.
-
-
Replying to @edsu
Not laying claim on ours. Just ignoring our work. Check out the JSON on that page, btw. And the early recognition, further down, re the need for interoperability when expressing traces/behaviors http://tracer.mementoweb.org/
1 reply 0 retweets 1 like -
-
-
-
So when is it all getting deployed into archive-it and webrecorder? Or is it not just a technical problem? Speaking of my PhD work...
1 reply 0 retweets 1 like -
Limited release of demo system+browser extension soon (happy to share w/ you). More detailed video screen captures available next week too. All Prototype though. IA and WR are aware.
1 reply 1 retweet 3 likes -
Replying to @mart1nkle1n @hvdsomp
Nice. Good luck! While I had seen Memento Tracer before I only recently found out about behaviors in Brozzler, which according to GitHub date back at least till July of 2015. https://github.com/internetarchive/brozzler/commits/master?after=809ea3885ffa1a9e2db9058f83b5e468e9724203+34&path%5B%5D=brozzler&path%5B%5D=behaviors.yaml …
#liveandlearn1 reply 0 retweets 1 like -
I think point
@edsu was making was about interoperability/standardization of automated behavior systems, something I've also suggested but is easier said than done. For example, both Brozzler and LOCKSS both have automated behavior systems, and we are developing one for WR1 reply 0 retweets 5 likes -
Replying to @IlyaKreymer @edsu and
They each have unique requirements and constraints, and slightly different implementation stacks. Tracer takes a uniquely different approach and introduces a visual scripting component instead of hand scripted behaviors. While this is very interesting and promising 1/2
1 reply 0 retweets 2 likes
that doesn't really make it interoperable with previous approaches. Arguably, a new approach makes interoperability with the previous solutions harder, not easier. Interop requires close collaboration, and investment both technical and political, esp. given limited resources 2/2
-
-
As you know, system interop and standards dev is a big part of what we do, hence at the forefront of our thinking when developing new systems. I assume you are not arguing against a diverse landscape of interoperable and standards-compliant systems?
1 reply 0 retweets 0 likes -
I don't hear
@ilyakreymer arguing against diversity and interop. i hear him saying that successful standards are grown from people wanting to work together collaboratively. Hopefully the prototype you've built will generate that. If not, back to the drawing board, together.1 reply 0 retweets 3 likes - 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.