-
Given the heterogeneous community of participants and technologies, the library is being developed with two key notions: a spectrum of interoperability and one library, many portals
The following diagram, extracted from the architecture document, is also very helpful:
Given this architectural diagram, I would think the ScholarsBox would be a type of "portal" (except that as a desktop client, it would not be communicating to users via HTTP). The ScholarsBox would need speak SDLIP -- and maybe SDSQL, which is mentioned in
Search and Discovery Services: Architecture (probably a naive question -- but why another query language instead of adopting a more standard approach like
XQuery, as recommended by the IMS-DRI specification?)
I've learned later that there are options other than SdliProtocol for ScholarsBox to use. I'm working the details out at ScholarsBox/NsdlIntegration.
On second thought, perhaps the ScholarsBox, as a provider of services, would be sitting in the "Services box" and therefore perhaps need to become a SDLIP and SDSQL server. I couldn't figure out the answer by reading the architecture diagram.
