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>OslcCommonArchitecture? >OslcCommonNeeds (revision 11)

OSLC Cross-Domain Needs

As separate domain activities evolve, patterns emerge to solve some integrations challenges. These patterns need to be identified and potentially promoted to a more general purpose specification that applies to most domains. The table below will identify these patterns in existing specifications today and look for candidates to emerge into cross-domain specifications. These specifications can then be adopted directly within various domains, either directly or by providing extensions.

Integration Patterns

Domain leads will update this table by adding new patterns (rows) and by indicating what patterns they are currently leveraging. As new specifications are being developed, please make sure to update this table.

Pattern CM Sort RM Sort QM Sort ArchM Sort AM Sort SCM Sort Metrics Sort Reporting Sort
Service Discovery (Catalogs) R R R R   R R R
Service Discovery (Description Documents) S C C C   R R R
Simple GET-based query syntax S C C N   C R R
Selective retrieval of resource properties S   C     C R R
Selective update of resource properties S   C          
Delegated resource creation S C C C        
Delegated resource selection S C C C   C    
Delegated query builder N         C    
RESTful CRUD of resources S C C C   C    
Resource link label attribute S   C          
XML resource collection formats S C C C   C    
XML resource collection formats - pagination S C C C   C    
XML resource link formats N C C C   C    
JSON representations S C            
Error responses S   N R   C    
Discussion resource N              
Project resource N              
Attachment resource N              
Property description               N

S - Specification (originated in this domain)
C - Copied (copied from another domain specification, actively being spec'd)
N - Need (no specification being develop yet)
R - Reused (leveraging an existing specification)

Edit | Attach | Print version | History: r15 | r13 < r12 < r11 < r10 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r11 - 10 Feb 2010 - 20:03:14 - ArthurRyman
This site is powered by the TWiki collaboration platform 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