DRAFT NSF Site Visit DataSpace Review: Microsoft Presentation 8 Feb 2010 (v5)

1. DataSpace DRAFT NSF Site VisitDataSpace Review: Microsoft Presentation 8 Feb 2010 (v5)

2. Why is Microsoft Interested in DataSpace • Large-scale data-driven sciences requires significant investments in hardware and software infrastructure • Advances in data storage, processing and information extraction are critical success factors, and fundamentally change how science gets done • Microsoft is interested in participating in developing breakthrough technologies • Microsoft is building a life-sciences platform (Amalga Life Sciences) with similar requirements • Including research on federated cross domain authentication and access control

3. Microsoft Research Experience • Individuals involved in this project have broad and relevant research experience. Participants’ include: • Dr. Steven White: 3D registration and imaging platform architecture • Dr. Allen Brown: Life-sciences computational platforms and data security • Dr. Antonio Criminisi: Anatomical labeling from 3D data and image recognition • Dr. Martin Will: Life-sciences data management, analytics, geometry and graphics processing.

4. Collaboration with Neuroscience Team • Microsoft will work with the DataSpace neuroscience team (e.g., Dr Gabrieli’s group): • Applying labeling and registration on neuroimaging data • Enabling cross-site data sharing and reuse. • Testing and evaluating platform architectures for remote data analysis

5. Collaboration on Architecture • The DataSpace system will be developed in an open collaboration between teams to enable sharing of both data and algorithms while allowing parties to protect the privacy and integrity of each. • Microsoft’s Amalga platform is a federated and loosely coupled architecture ideally suited for research programs like DataSpace • Microsoft will encourage and support adoption of open standards (e.g. RDF, SPARQL) to facilitate interoperation of systems and sharing of data and algorithms.

6. Backup slide

7. Microsoft Approach to Claims Based Security Token: A cryptographically signed data unit that expresses one or more claims. • Single sign on • Decouple services from authentication • Support different types of credentials • Support federated scenarios for cross domain authentication and access control • Facilitate identity delegation • Facilitate claim mapping Identity Provider Secure Token Service (STS) 4) Token issued with claims 3) Authenticate, Acquire Token 5) Invoke Service using the claims Service User Service (Relying Party 1) Acquire claim requirements 2) Return claim requirements

8. Image /Ontology Mapping Scenarios