On Mar 6, 2014, at 1:37 PM, Ethan Gruber ewg4x...@gmail.com wrote:
Let me ask a more direct question. If participating in linked data is a
“good thing”, then how do you — anybody here — suggest archivists (or
librarians or museum curators) do that starting today? —Eric Morgan
I think that
I’m just curious. To what degree does ArchiveSpace support publishing content
as linked data? Transforming EAD (or MARC) into serialized RDF is functional
but not ideal for linked data, for many reasons. ArchiveSpace as a content
management system may be more feasible. At the very least,
ArchivesSpace has a REST backend API, and requests yield a response in
JSON. As one option, I'd investigate to publish linked data as JSON-LD.
Some degree of mapping would be necessary, but I imagine it would be
significantly easier to that instead of using something like D2RQ.
Mark
--
Mark A.
On Mar 6, 2014, at 9:47 AM, Mark A. Matienzo mark.matie...@gmail.com wrote:
ArchivesSpace has a REST backend API, and requests yield a response in
JSON. As one option, I'd investigate to publish linked data as JSON-LD.
Some degree of mapping would be necessary, but I imagine it would be
The issue here that I see is that D2RQ will expose the MySQL database
structure as linked data in some sort of indecipherable ontology and the
end result is probably useless. What Mark alludes to here is that the
developers of ArchivesSpace could write scripts, inherent to the platform,
that could
, 2014 10:42 AM
To: CODE4LIB@listserv.nd.edu
Subject: Re: [CODE4LIB] ArchivesSpace v1.0.7 Released [linked data]
On Mar 6, 2014, at 9:47 AM, Mark A. Matienzo mark.matie...@gmail.com wrote:
ArchivesSpace has a REST backend API, and requests yield a response in
JSON. As one option, I'd investigate
On Thu, Mar 6, 2014 at 11:05 AM, Ethan Gruber ewg4x...@gmail.com wrote:
The issue here that I see is that D2RQ will expose the MySQL database
structure as linked data in some sort of indecipherable ontology and the
end result is probably useless. What Mark alludes to here is that the
On Thu, Mar 6, 2014 at 11:05 AM, Ethan Gruber ewg4x...@gmail.com wrote:
What Mark alludes to here is that the developers of ArchivesSpace could
write scripts, inherent to the platform, that could output linked data that
conforms to existing or emerging standards. This is much simpler than
Let me ask a more direct question. If participating in linked data is a “good
thing”, then how do you — anybody here — suggest archivists (or librarians or
museum curators) do that starting today? —Eric Morgan
I think that RDFa provides the lowest barrier to entry. Using dcterms for
publisher, creator, title, etc. is a good place to start, and if your
collection (archival, library, museum) links to terms defined in LOD
vocabulary systems (LCSH, Getty, LCNAF, whatever), output these URIs in the
HTML
10 matches
Mail list logo
