1 / 10

Foundation top ~5 issues

Foundation top ~5 issues. Scott’s Top 6 Messy Items. Read ACLs. Authentication and delegated auth. What is a “Project”?. URL Design, representations. Application runtime model. Query language, runtime, performance. De-Normalized resources (DTO’s). Read ACLs - Scott.

lucien
Download Presentation

Foundation top ~5 issues

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Foundation top ~5 issues

  2. Scott’s Top 6 Messy Items Read ACLs Authentication and delegated auth What is a “Project”? URL Design, representations Application runtime model Query language, runtime, performance De-Normalized resources(DTO’s)

  3. Read ACLs - Scott • The Foundation will provide Read access control at a Security Context (Project, Team may be examples) • Requires a URL be mappable to a Security Context (the faster the better) • Can Applications further constrain read access? • Requires that we give apps exclusive control of reads • Needs a Storage Service and RTC solution

  4. Application Runtime Model - James • This must solve the DTO problem by allowing you to write code to produce one or more de-normalized forms from the normalized form which is also available to clients • Multi-get might be a variant of this • Java-based, Jazz Foundation provided • Hard problem: read ACLs for a composite • Don’t invent anything • Thought exercise: RTC, RRC, RQM arrive as VMWare images, you fire them up and they hook into discovery and admin

  5. 1A’. App-specific implementation of REST API Client App logic RESTAPI Dumb data store App data Storage App RESTAPI • Basics • Client talks to apps through REST APIs • Apps talk to dumb data store • Clients to not access data store directly

  6. URL Design,representations - Ed • Input from Bill • Tension between URL stability and ability to see context in the URL • Maybe we can separate stable URIs and pretty URLs which include context

  7. What is a “Project”? - Kai • Consensus on projects of projects and relationships between them • Requirements project->Dev Project->Test project • Can we continue with Project Area as a place to do many Projects? • “Project” gets closer to PMI def. short-term, people come together and produce a deliverable • AIG discussion supported this direction • We could support a project-less product, like a Glossary tool. It would want an associated security context, teams, users, roles and permissions. • Explore mapping Jazz Project into the new model, dev lines may transform into sub-projects

  8. Authentication and delegated auth - Pat • Focus on server-to-server • Reconcile with Ed’s solution • Hopefully DAFilter is a good start

  9. Query language, runtime, performance – Simon • What to do after XQuery? • Work with IM

  10. Linking – James • Resource formats for links • Embedded • Free-standing • Permissions for links • Query for embedded back-links • Tagging and navigation, bookmarks

More Related