Hi Ben. Following the id.loc.gov approach makes a lot of sense. Thanks
for suggesting it!
On Wed, Dec 20, 2017 at 10:30 AM, Benjamin Armintor wrote:
> Daniel,
>
> Have you though about the approach id.loc.gov uses? It's recognizable file
> extensions, with the application distinguished as necessa
Daniel,
Have you though about the approach id.loc.gov uses? It's recognizable file
extensions, with the application distinguished as necessary e.g.:
http://id.loc.gov/authorities/subjects/sh2008104251 an identifier,
redirecting to http://id.loc.gov/authorities/subjects/sh2008104251.html, a
serial
If we can find any clients that actually make use of embedded JSON-LD, I'd
look at how they would treat it. If we can't, then i guess that says
something.
On Tue, Dec 19, 2017 at 1:33 PM, Daniel Lovins
wrote:
> Dear community,
>
> We have a project underway at NYU called "Enhanced Networked
> Mo
Dear community,
We have a project underway at NYU called "Enhanced Networked
Monographs" [1] that uses topic maps [2] to merge back-of-book indexes
from about 100 open-access monographs, provides an editorial interface
through a Topic Curation Toolkit, and provides a user interface
through the Rea
