Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Passage and passage references methods should be identifier agnostic #27

Closed
PonteIneptique opened this issue May 24, 2016 · 2 comments
Closed

Comments

@PonteIneptique
Copy link
Member

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 :

  1. CTS URN Namespace is not registered
  2. There is no international registry
  3. 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

  1. A CTS provider want to be DTS compatible, and so DTS should accept CTS URN
  2. An archival institution has transcripts of archives and has its own identifier system, but wants to display and give access to the textual content
  3. A small journal gives access to articles using the ISBN of the journal and some other internal identifier for the specific issue
  4. Any institution wants to give API access using DOIs such as zenodo's one

Examples

  1. 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
  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
@PonteIneptique 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
@PonteIneptique
Copy link
Member Author

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

@PonteIneptique
Copy link
Member Author

For cleaning reason, we are closing old issues.
Please feel free to comment if you think we should reopen.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant