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 <[log in to unmask]> wrote:
> 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
> serialization linking to
> http://id.loc.gov/authorities/subjects/sh2008104251.skos.json, a json-ld (I
> think) representation of the subject as a SKOS concept, etc..
>
> I'm also lazy enough that I'd try to avoid that '+' in the URI if possible.
>
> - Ben
>
> On Tue, Dec 19, 2017 at 1:33 PM, Daniel Lovins <[log in to unmask]>
> wrote:
>
>> 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 Readium ebook platform.
>>
>> We are using JSON-LD and Web Annotation for modeling the topic map,
>> and annotating topic pages accordingly.
>>
>> We wanted to ask this group if it make sense to embed limited JSON-LD
>> into our topic webpages (e.g. at a URL such as
>> https://enm.dlib.nyu.edu/topic/2938) and then provide a full JSON-LD
>> record (at a URL such as https://enm.dlib.nyu.edu/data/2938/ld+json),
>> as shown in our examples [3].
>>
>> It seems reasonable to us based on the content negotiation principles
>> described in the W3C's "Cool URIs for the Semantic Web [4], but we'd
>> like to know if there are other considerations to be aware of.
>>
>> Thanks for your help!
>>
>> Daniel
>>
>>
>> [1] https://wp.nyu.edu/enmproject/
>>
>> [2] https://en.wikipedia.org/wiki/Topic_map
>>
>> [3] https://docs.google.com/document/d/1Bbn0iCiRUNoULnOB9f46dYZfBS6yl
>> 5OKbXp6SVz-Jas/edit
>>
>> [4] https://www.w3.org/TR/cooluris/#r303uri
>>
>> --
>> Daniel Lovins
>> Head of Knowledge Access, Design & Development
>> Knowledge Access & Resource Management Services
>> New York University, Division of Libraries
>> 20 Cooper Square, 3rd floor (311)
>> New York, NY 10003-7112
>> [log in to unmask]
>> 212-998-2489
>>



-- 
Daniel Lovins
Head of Knowledge Access, Design & Development
Knowledge Access & Resource Management Services
New York University, Division of Libraries
20 Cooper Square, 3rd floor (311)
New York, NY 10003-7112
[log in to unmask]
212-998-2489