1,496
edits
mNo edit summary |
|||
Line 9: | Line 9: | ||
* Finally, can we think of these functions as a layer on top of mere archives, and construct them as a physically separate service? | * Finally, can we think of these functions as a layer on top of mere archives, and construct them as a physically separate service? | ||
** How would such a service integrate with layers below (archives) and above (editorial, exploration)? | ** How would such a service integrate with layers below (archives) and above (editorial, exploration)? | ||
Addressability is a first technical barrier: | |||
* Being able to construct links between multiple representations of the same documents | |||
** Across mirrors (same content, same addressing scheme, different location) | |||
** Across types of archive browsers (some may have further annotations, all may have different addressing schemes, all will have different locations) | |||
* Being able to identify existing references/annotations by detecting such links | |||
** E.g. via Twitter/Google search | |||
Note: | Note: | ||
Line 15: | Line 22: | ||
== Exemplary Publications == | == Exemplary Publications == | ||
Look out for: | Look out for: | ||
Line 114: | Line 114: | ||
** Though don't make it too complex. Core use case: WikiLeaks text archives | ** Though don't make it too complex. Core use case: WikiLeaks text archives | ||
* Would like to offer editorial tools in a manner that they can easily be integrated on other sites, e.g. as part of an editorial publication | * Would like to offer editorial tools in a manner that they can easily be integrated on other sites, e.g. as part of an editorial publication | ||
** This infrastructure is plumbing, not a product in itself. It only becomes useful by feeding into and strengthening existing editorial processes. | |||
=== Editorial Functions === | === Editorial Functions === |