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.
On Tue, Dec 19, 2017 at 1:33 PM, Daniel Lovins <[log in to unmask]>
> Dear community,
> We have a project underway at NYU called "Enhanced Networked
> Monographs"  that uses topic maps  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 .
> It seems reasonable to us based on the content negotiation principles
> described in the W3C's "Cool URIs for the Semantic Web , but we'd
> like to know if there are other considerations to be aware of.
> Thanks for your help!
>  https://wp.nyu.edu/enmproject/
>  https://en.wikipedia.org/wiki/Topic_map
>  https://docs.google.com/document/d/1Bbn0iCiRUNoULnOB9f46dYZfBS6yl
>  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]