point well taken. :)
there were no significant changes to the WARC format
between the last draft and the published standard.
you can use Heritrix WARCReader, or WARC Tools warcvalidator
to verify that you have created a valid WARC in accordance
with the spec.
/st...@archive.org
On 6/2/09 2
hi Karen,
understood.
the final draft of the spec is available here:
http://www.scribd.com/doc/4303719/WARC-ISO-28500-final-draft-v018-Zentveld-080618
and other (similar) versions here:
http://archive-access.sourceforge.net/warc/
/st...@archive.org
On 6/2/09 2:15 PM, Karen Coyle wrote
hi code4lib,
if you're archiving web content, please use the WARC format.
thanks,
/st...@archive.org
WARC File Format Published as an International Standard
http://netpreserve.org/press/pr20090601.php
ISO 28500:2009 specifies the WARC file format:
* to store both the payload conten
at the settlement could give
_only_ Google the right to scan orphaned works, and no
one else. that certainly wouldn't help libraries.
/st...@archive.org
migrate occasionally for maintenance.
/st...@archive.org
On 5/19/09 10:51 AM, raj kumar wrote:
On May 19, 2009, at 10:40 AM, Eric Lease Morgan wrote:
On May 19, 2009, at 1:24 PM, Eric Lease Morgan wrote:
I applaud the Internet Archive and the Open Content Alliance's
efforts. archive.org++
fyi - [the Google Book Settlement] "should not be approved"
A Book Grab by Google
by Brewster Kahle
Tuesday, May 19, 2009
Washington Post | Opinions
http://www.washingtonpost.com/wp-dyn/content/article/2009/05/18/AR2009051802637.html
/st...@archive.org
rners think about how to get information and solve problems.
i think it's exciting to think that it could steer learners and
researchers away from looking to the web (unfortunately, almost
always Google by default) for quick answers, and back to
thinking about how they can answer questions for thems
like this.
/st...@archive.org
ux system
is organic, and the workforce is distributed and lasseiz-faire.
it doesn't seem to be very agile in responding to monolithic
deficiencies (just look at how we ended up with the linux
kernel vs. hurd :).
/st...@archive.org
ux system
is organic, and the workforce is distributed and lasseiz-faire.
it doesn't seem to be very agile in responding to monolithic
deficiencies (just look at how we ended up with the linux
kernel vs. hurd :).
/st...@archive.org
On 12/30/08 12:37 PM, Darrell Eifert wrote:
Hi Folks --
10 matches
Mail list logo
