This wiki is locked. Future workgroup activity and specification development must take place at
our new wiki
. For more information, see
this blog post about the new governance model
and
this post about changes to the website
.
TWiki
>
Main Web
>
CmHome
>
CmArchitecturalDirectionV2
(revision 1) (raw view)
---+ OSLC CM Architectural Direction _Working document - supporting specification development_ The purpose of this page is to collect the architectional direction as driven by scenario priorities for the next version of CM specifications (V2). It also contains various 1.0 issues to be addressed in the next version. ---++ Items for consideration for post-1.0 <strong>Better handling of differing authenication models<br /></strong>We've run into some issues when clients don't always know when and how to handle form auth, like when using a batch-mode RESTful interface (feed readers, etc). *Alignment of related standards*: * [[http://en.wikipedia.org/wiki/ICalendar#To-do_.28VTODO.29][VTODO]] - need to consider aligning with task management tools? * [[http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/OpenSocial-Specification.html][OpenSocial]] - need to evolve our delegated UIs to a widget spec when it is available? * [[http://en.wikipedia.org/wiki/Web_Services_Description_Language][WSDL 2.0]] - RESTful service description <strong>Presentation requirements for resources<br /></strong>Some implementations have assumed different models for what HTML should be returned when requested: should it be contained in an IFrame with just dialog for change request viewing and editing? should it be its own page, with application banner and navigation bar? <strong>Reverse service discovery<br /></strong>Since resources are URL-addressable, they often get pasted into tools without going through service discovery. A possible solution would be to support requesting the service discovery document an the change request resource URI: * Performing a HEAD operation on the URI could return at least the CR and service document content types, then consumer would know that the URI is an OSLC one. * Performing a GET operation on the URI with Accept header being x-oslc-cm-service-description+xml would return the service description document, not the chang request or by embedding the service discovery doc URL in the change request resource definition *Named/Pre-defined Queries* <br />Most, if not all, CM systems have the ability for a user to create a named query to be accessed later for execution. We could fairly rapidly provide at least read-only access to these and execution of queries. *Delegated Service Discovery* <br /> - better handling of configuration data<br /> - better scaling *Reportable REST* <br /><br /> *Linking issues:* <br /> - no good way in C/ALM 1.0 to remove the back link
Edit
|
Attach
|
P
rint version
|
H
istory
:
r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Raw edit
|
More topic actions...
Topic revision: r1 - 23 Jun 2009 - 13:54:47 -
SteveSpeicher
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use
Ideas, requests, problems regarding this site?
Send feedback