You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, CTS is identifer dependent, as it requires a CTS URN. Main arguments against CTS are actually often oriented around this central piece in CTS :
CTS URN Namespace is not registered
There is no international registry
The model is not compliant with my work (textgroup.work.version) or hard to fit into
What to do and why
While I do personally believe CTS URN are a nice system and I also think DTS should be CTS URN compatible, I think the only way to go further and bring more people than classicists and mediaevalists is to leave CTS URN as one of the option we provide but not the main one. This is the only way to bring more development power into this project and more adoption.
User stories
A CTS provider want to be DTS compatible, and so DTS should accept CTS URN
An archival institution has transcripts of archives and has its own identifier system, but wants to display and give access to the textual content
A small journal gives access to articles using the ISBN of the journal and some other internal identifier for the specific issue
Any institution wants to give API access using DOIs such as zenodo's one
Examples
With CTS URN
/api/dts/references/urn:cts:latinLit:phi1294.phi002.perseus-lat2 gets a list of references
/api/dts/passages/urn:cts:latinLit:phi1294.phi002.perseus-lat2 gets the whole text
/api/dts/passages/urn:cts:latinLit:phi1294.phi002.perseus-lat2/1.1-1.2 get the range 1.1-1.2 [ Note the difference with current cts implementation which uses : 1.1-1.2
With ARK (Small change to identifier system replace slash with colons) resource
/api/dts/references/ark:12148:bpt6k107371t gets a list of references
/api/dts/passages/ark:12148:bpt6k107371t gets the whole text
/api/dts/passages/ark:12148:bpt6k107371t/1.1-1.2 get the range 1.1-1.2
The text was updated successfully, but these errors were encountered:
PonteIneptique
changed the title
Passage and passage references method should be identifier agnostic
Passage and passage references methods should be identifier agnostic
May 24, 2016
Note that it could be up to the implementer to write a conversion system for rerouting /api/dts/passages/urn:cts:latinLit:phi1294.phi002.perseus-lat2:1.1-1.2 to /api/dts/passages/urn:cts:latinLit:phi1294.phi002.perseus-lat2/1.1-1.2
Current status
Right now, CTS is identifer dependent, as it requires a CTS URN. Main arguments against CTS are actually often oriented around this central piece in CTS :
What to do and why
While I do personally believe CTS URN are a nice system and I also think DTS should be CTS URN compatible, I think the only way to go further and bring more people than classicists and mediaevalists is to leave CTS URN as one of the option we provide but not the main one. This is the only way to bring more development power into this project and more adoption.
User stories
Examples
/api/dts/references/urn:cts:latinLit:phi1294.phi002.perseus-lat2
gets a list of references/api/dts/passages/urn:cts:latinLit:phi1294.phi002.perseus-lat2
gets the whole text/api/dts/passages/urn:cts:latinLit:phi1294.phi002.perseus-lat2/1.1-1.2
get the range1.1-1.2
[ Note the difference with current cts implementation which uses :1.1-1.2
/api/dts/references/ark:12148:bpt6k107371t
gets a list of references/api/dts/passages/ark:12148:bpt6k107371t
gets the whole text/api/dts/passages/ark:12148:bpt6k107371t/1.1-1.2
get the range1.1-1.2
The text was updated successfully, but these errors were encountered: