Page History
...
Name | Role | Present |
---|---|---|
Wright, Larry | NIH/NCI | x |
Fragoso, Gilberto | NIH/NCI | x |
De Coronado, Sherri | NIH/NCI | x |
Safran, Tracy | NIH/NCI [C] | x |
Ong, Kim L | IS | x |
Lucas, Jason R | IS | x |
Bauer, Scott | Mayo | x |
Stancl, Craig | Mayo | x |
Endle, Cory | Mayo | x |
Solbrig, Harold | Mayo | x |
Jiang, Guoqian | Mayo | x |
Wynne, Robert | NIH/NCI [C] | |
Tran, Tin | NIH/NCI [C] | |
Carlsen, Brian | NIH/NCI [C] | |
Wong, Joanne | NIH/NCI [C] | |
Kuntipuram, Kumar | NIH/NCI [C] |
|
Haber, Margaret | NIH/NCI | x |
Campbell, John | NIH/NCI | x |
AgendaGoals
...
- LexEVS
...
- and CTS2 are planned to continue as key components of NCI terminology services, but NCI also plans to extend beyond them, notably with RDF triple store SPARQL and REST components. This raises important design and coordination issues.
- REST services need substantial extensions, within and beyond CTS2. NCI plans to offer REST APIs that can support the requirements of its own and others’ applications, and expects a significant component to be REST services from the RDF triple store. An obvious test case is ability to support EVS browser functionality (even while these browsers will likely use the Java API for some time to come).
- We face some immediate needs from other users, notably CTRP and GDC, so need to clarify design approaches and produce new services based on them in the relatively near term.
Agenda
Continue discussion around what is missing from current REST CTS2 service. (All) |
|
Next Steps |
|
...