On Sat, Jan 25, 2014 at 6:20 AM, Jon Phipps wrote:
> On Fri, Jan 24, 2014 at 11:16 AM, Robert Sanderson >wrote:
>
> > > All in my opinion, and all debatable. I hope that your choice goes well
> > > for
> > > > you,
> > >
> > > I'd
(Sorry for a previous empty message)
Hi Jon,
On Fri, Jan 24, 2014 at 7:56 AM, Jon Phipps wrote:
> Hi Rob, the conversation continues below...
>
> On Thu, Jan 23, 2014 at 7:01 PM, Robert Sanderson >wrote:
> > To present the other side of the argument so that others on the li
On Fri, Jan 24, 2014 at 7:56 AM, Jon Phipps wrote:
> Hi Rob, the conversation continues below...
>
> On Thu, Jan 23, 2014 at 7:01 PM, Robert Sanderson >wrote:
>
> > Hi Jon,
> >
> > To present the other side of the argument so that others on the list
Hi Jon,
To present the other side of the argument so that others on the list can
make an informed decision...
On Thu, Jan 23, 2014 at 4:22 PM, Jon Phipps wrote:
> I've developed a quite strong opinion that vocabulary developers should not
> _ever_ think that they can understand the semantics of
P166123464771
And now no one understands at all. CIDOC-CRM has taken the same approach
-- it's better that everyone is equal in their non-comprehension than
people who speak a particular language are somehow advantaged.
BTW, as an English speaker, I also don't understand "other designation
a
Have you considered the LOCAH work in mapping EAD into Linked Data?
http://archiveshub.ac.uk/locah/
and
http://data.archiveshub.ac.uk/
Rob
On Sun, Jan 19, 2014 at 5:10 PM, Ben Companjen
wrote:
> Hi Eric,
>
> While I'm no archivist by training (information systems engineer I am),
> I've learn
> On Tue, Jan 14, 2014 at 12:17 PM, L Snider wrote:
>
> > Rob is right on! I included the wrong link, thanks for catching that...
> >
> > Cheers
> >
> > Lisa
> >
> >
> > On Tue, Jan 14, 2014 at 11:04 AM, Robert Sanderson > >wrote:
> &
For what it's worth, the latest wayback code is:
https://github.com/iipc/openwayback
And being developed by the IIPC consortium, rather than just the Internet
Archive alone.
It has many additional features, contributed by other members.
It should be used in preference to the sourceforge vers
To be (more) controversial...
If it's okay to require headers, why can't API keys go in a header rather
than the URL.
Then it's just the same as content negotiation, it seems to me. You send a
header and get a different response from the same URI.
Rob
On Mon, Dec 2, 2013 at 10:57 AM, Edward Su
On Sun, Dec 1, 2013 at 5:57 PM, Barnes, Hugh wrote:
> +1 to all of Richard's points here. Making something easier for you to
> develop is no justification for making it harder to consume or deviating
> from well supported standards.
>
I'm not suggesting deviating from well supported standards, I'
Hi Richard,
On Sun, Dec 1, 2013 at 4:25 PM, Richard Wallis <
richard.wal...@dataliberate.com> wrote:
> "It's harder to implement Content Negotiation than your own API, because
> you
> get to define your own API whereas you have to follow someone else's rules"
> Don't wish your implementation prob
(posted in the comments on the blog and reposted here for further
discussion, if interest)
While I couldn't agree more with the post's starting point -- URIs identify
(concepts) and use HTTP as your API -- I couldn't disagree more with the
"use content negotiation" conclusion.
I'm with Dan Cohen
Hi Andrew,
Not exactly sure what sort of differences you're after...
Do you mean the difference between this:
http://iipimage.sourceforge.net/documentation/protocol/
(and it's 74 page reference: http://iipimage.sourceforge.net/IIPv105.pdf )
And this:
http://www-sul.stanford.edu/iiif/image-
n their own individual graphs,
> won't that be chaos? I really don't know the answer, it's not a rhetorical
> question!
>
> Hugh
>
> On Nov 6, 2013, at 10:40 , Robert Sanderson wrote:
>
> > Named Graphs are the way to solve the issue you bring up in that pos
Named Graphs are the way to solve the issue you bring up in that post, in
my opinion. You mint an identifier for the graph, and associate the
provenance and other information with that. This then gets ingested as the
4th URI into a quad store, so you don't lose the provenance information.
In JSO
Yes, I'm going to get sucked into this vi vs emacs argument for nostalgia's
sake.
>From the linked, very outdated article:
> In fact, as far as I know I've never used an RDF application, nor do I
know of any that make me want to use them. > So what's wrong with this
picture?
a) Nothing. You wo
You're still missing a vital step.
Currently your assertion is that the creator /of a web page/ is Jefferson,
which is clearly false.
The page (...) is a transcription of the Declaration of Independence.
The Declaration of Independence is written by Jefferson.
Jefferson is Male.
And it's not ver
Dear all,
We are delighted to be able to announce the availability of the beta
Memento extension for Chrome. The extension is available in the Chrome
store:
https://chrome.google.com/webstore/detail/memento/jgbfpjledahoajcppakbgilmojkaghgm?hl=en&gl=US
Below, we include the description that accom
+1, of course :)
You might wish to consider some further derivatives/related pages:
http://www.diglib.org/about/code-of-conduct/
http://wikimediafoundation.org/wiki/Friendly_space_policy
https://thestrangeloop.com/about/policies
http://www.apache.org/foundation/policies/anti-harass
I guess that you need to be logged in to vote?
Perhaps a direct link in the text to where to login, and where to request a
new account?
Thanks,
Rob
On Tue, Nov 13, 2012 at 11:15 AM, Becky Yoose wrote:
> Not a voting problem per se, but the results page in IE9 [1] in Win7 threw
> up up everywh
Have you considered Shared Canvas? Foldouts, flaps, curtains and all sorts
of interactive zones formed a significant part of our design use cases and
requirements.
http://www.shared-canvas.org/
Rob
On Feb 15, 2012 12:49 PM, "Sara Amato" wrote:
> Thanks for this example - I'll follow up with the
+1
Rob
On Thu, Jan 12, 2012 at 9:26 AM, aj...@virginia.edu wrote:
> My inclination would be to keep the descriptive snippets in some kind of
> content store with a good RESTful Web exposure and just use those URLs as the
> values of "description" triples in your RDF. Then your RDF is genteel L
You might consider the Content in RDF specification:
http://www.w3.org/TR/Content-in-RDF10/
which describes how to do this in a generic fashion, as opposed to
stuffing it directly into a string literal.
HTH
Rob
On Wed, Jan 11, 2012 at 12:36 PM, Ethan Gruber wrote:
> Hi all,
>
> Suppose I h
I know the guys that work at Findings, and it would be a great team to
work in, doing cool stuff :)
Rob
On Mon, Jan 9, 2012 at 2:50 PM, Jodi Schneider wrote:
> https://findings.com/jobs
On Thu, Dec 8, 2011 at 9:14 AM, BRIAN TINGLE
wrote:
> On Dec 7, 2011, at 2:19 PM, Robert Sanderson wrote:
>> * Lax Security -- It's easier to get into trouble when you're simply
>> inlining HTML received, compared to building the elements. Getting
>> into the s
Here's some off the top of my head:
* Separation of concerns -- You can keep your server side data
transfer and change the front end easily by working with the
javascript, rather than reworking both.
* Lax Security -- It's easier to get into trouble when you're simply
inlining HTML received, comp
LibLime
A Division of PTFS, Inc.
Main Office
11501 Huff Court
North Bethesda, Maryland 20895
tel: (301) 654-8088 Ext. 127
fax: (301) 654-5789
email: kohai...@liblime.com
Twitter: @liblime
How about we all contact them? ;)
Rob
2011/11/23 Wilfred Drew :
> Has anybody contacted the company? A s
Without /any/ infrastructure it would be a challenge, but a simple
database that has timestamps and basic metadata would be sufficient.
The timestamps are the most important, obviously, to populate the feed
correctly and handle the time slicing.
Rob
On Tue, Jun 21, 2011 at 8:55 AM, Eric Lease Mor
Dear all,
We have published an updated internet draft for the Memento
specification concerning Time Travel on the Web.
It is available at:
* TXT version: http://www.ietf.org/id/draft-vandesompel-memento-01.txt
* HTML version: http://mementoweb.org/guide/rfc/ID/
This version contains updates and
It can also be both, by the way. The OCR or text can be hidden behind
the image, but selectable.
Or it can have both image and text, but the text isn't selectable.
This enables searching without being able to cut and paste the text.
In other words, IMO you should just describe the situation you h
Our work on Memento comes to mind, of course.
http://www.mementoweb.org/
And in particular, regarding the second point, our papers about the
use of Memento for non-traditional interactions with web archives:
* http://arxiv.org/abs/1003.3661
Using Memento to recover the state of a web resource at
-- Forwarded message --
From: Christine McWebb
Date: Mon, Apr 18, 2011 at 7:36 AM
Subject: [dm-l] Postdoctoral Fellowship at MARGOT, University of Waterloo
To: d...@uleth.ca
University of Waterloo – Mellon Postdoctoral Fellowship in Digital Humanities
With apologies for cross-
Forwarded:
The Open Annotation Collaboration (OAC) project is pleased to announce
a Request For Proposal to collaborate with OAC researchers for
building implementations of the OAC data model and ontology. The OAC
is seeking to collaborate with scholars and/or librarians currently
using and/or cur
That is (still) incorrect.
A single schema may contain multiple namespaces, and there isn't a
unique identifier for a schema. For example, any simple Dublin Core
based syntax must have at least two Namespaces, Dublin Core and the
wrapper element. SchemaLocation is not unique as there can be many
On Mon, Dec 20, 2010 at 1:28 PM, BRIAN TINGLE wrote:
>
> "graph processing stack on top of a graph database" resonates with me more
> than "RDF store with SPARQL access" but I guess they are
> basically/functionally saying the same thing? Maybe the "graph database"
> way of thinking about it is
Dear all,
The Open Annotation Collaboration (OAC) project is pleased to announce
an open call for statements of interest in participating in the Using
the OAC Model for Annotation Interoperability Workshop. The workshop
will be held 24-25 March 20011 in Chicago, IL and will provide an in-
depth in
Agreed.
The easiest way, IMHO of working with EAD for several years at the Archives
Hub (http://www.archiveshub.ac.uk), would be to set up a set of EAD
templates and then cut and paste the text into them from Word.
Rob
On Thu, Oct 7, 2010 at 11:58 AM, Eric Lease Morgan wrote:
> On Oct 7, 2010,
I have apparently been taken in by the REST koolaid, as for a long
time I would have completely agreed with Ralph.
However it seems to me that a URI is an _Identifier_ for a resource,
which is orthogonal to the representations that it can provide on
demand, and any other such 'run time' requiremen
In today's RESTful world, what's the requirement for the httpAccept
parameter? Isn't straight content negotiation sufficient rather than
pulling the headers into the URI?
What happens if the accept header and the httpAccept parameter say
different things?
Rob
On Mon, May 17, 2010 at 1:37 PM, Le
Exposing the records as Linked Data, rather than just plain old XML
would be an interesting demonstration of how the library world can
generate and, more importantly, curate massive amounts of data. They
could then be linked to and from by other resources/services -- for
example linking a copy of
Depends on the sort of features required, in particular the access
patterns, and the hardware it's going to run on.
In my experience, NoSQL systems (for example apache's Cassandra) have
extremely good distribution properties over multiple machines, much
better than SQL databases. Essentially, it'
in your feedback. Discussions are welcomed on the
Memento list at <http://groups.google.com/group/memento-dev/>.
On behalf of the Memento team:
Herbert Van de Sompel - Los Alamos National Laboratory
Michael L. Nelson - Old Dominion University
Robert Sanderson - Los Alamos National Laboratory
42 matches
Mail list logo
