Internet2 is investigating a security incident involving a compromise to a confluence server that affected https://spaces.at.internet2.edu on April 10, 2019, which was successfully mitigated on April 12, 2019. If you did not receive an email from us, it’s unlikely that any of the content you submitted to the Internet2 Spaces Wiki needs to be re-entered. We apologize for any inconvenience this may have caused. Should you have any questions or require further assistance, please email email@example.com.
This working area is a broad investigation of the SOA and API spaces jointly. The popularity of commercial APIs, lightweight interfacing techniques have both overtaken and reinvigorated the need to apply SOA principles in the enterprise.
Working subgroups originating from an initial discussion are starting to take form. New participants and input is encouraged throughout.
Here is a simple draft taxonomy of the SOA API space based only on starting discussions. This overview will be useful to develop and refine as our interactions progress.
SOA API Stages
Areas of investigation
Determination of capabilities needed in an SOA API environment
Leveraging Business Drivers (Analytics, Evidence-based decisions, monetizing access to enterprise data)
Leveraging IT Drivers (better security, reduce complexity)
Investigation of overlap with teaching and learning
Enterprise data defintion and management
WS02 solution (selection, integrations, operations)
Design of common API across higher education
Securing APIs (authentication and especially authorization)
Messaging (role of ESB solutions, push vs pull direction)
Mobile device integration
Creating public APIs (use cases, balancing openness and resource control)
How to move enterprise from old techniques (ftp, direct database links) to SOA
Impact on data custodians and new governance opportunities