Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Architecture"

 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
__NOTOC__
+
=Goal=
[[Image:Higgins-v39.JPG]]
+
This page introduce architecture principles to be adopted by PolarSys projects and packages.
 +
It will describe the overall architecture of the PolarSys projects ecosystem.
 +
The Architecture Committee is linked to [http://wiki.eclipse.org/Polarsys/TLPProposal PolarSys Top Level Project].
  
[[Architecture Diagram Changes]] --changes to the above diagram
+
=Architecture Overview=
 +
To Be Done.
  
===Components===
+
=Policies=
* [[Higgins Browser Extension]]
+
[[PolarsysPolicies|PolarSys policies]] are a set of rules that should be adopted by PolarSys projects.
* [[RP Enablement]]
+
* [[I-Card Manager]]
+
* [[RP Protocol Support]]
+
* [[ISS Client UI]]
+
* [[I-Card Selector Service]] (ISS)
+
* [[I-Card Registry]]
+
* [[I-Card Provider]]
+
* [[Token Service]]
+
* [[Token Provider]]
+
* [[Identity Attribute Service]] (IdAS)
+
* [[Context Provider]]
+
  
===Clients/Consumers===
+
=Release Engineering=
Client apps and services that use these core components are expected to include:
+
This part describes the release engineering of Polarsys.
* Relying Party (Service Provider)s can use the "RP Enablement" component to add support (e.g. to validate tokens) for identity protoocols
+
* Local Apps (e.g. Eclipse RCP apps and other enterprise apps) can invoke a local instance of [[RP Protocol Support]] that uses a locally running [[ISS Client UI]] (card selector UI).  
+
  
==Links==
+
Topics:  
* [http://eclipse.org/higgins Higgins Home]
+
 
** [http://wiki.eclipse.org/index.php/Higgins_Wiki Wiki]
+
*[[Polarsys/Release_Engineering/Definitions|Definitions]]  
** [http://www.eclipse.org/higgins/faq.php FAQ]
+
*[[Polarsys/Release_Engineering/Policies|Policies]]
** [[Architecture]]
+
*[[Polarsys/Release_Engineering/Process|Process]]
** [[Components]]
+
 
** [http://www.eclipse.org/higgins/resources.php Developer Resources]
+
Interesting resources are already provided by the Eclipse LTS IWG:
** [http://www.eclipse.org/higgins/downloads.php Downloads]
+
 
 +
*[http://wiki.eclipse.org/LTS/LTS_Ready Description of Readiness for LTS]  
 +
*[http://wiki.eclipse.org/LTS#Value_Proposition LTS Value proposition]
 +
 
 +
=Work in progress=
 +
* [[Architecture/Interoperability | Interoperability]]

Latest revision as of 08:52, 10 September 2013

Goal

This page introduce architecture principles to be adopted by PolarSys projects and packages. It will describe the overall architecture of the PolarSys projects ecosystem. The Architecture Committee is linked to PolarSys Top Level Project.

Architecture Overview

To Be Done.

Policies

PolarSys policies are a set of rules that should be adopted by PolarSys projects.

Release Engineering

This part describes the release engineering of Polarsys.

Topics:

Interesting resources are already provided by the Eclipse LTS IWG:

Work in progress

Back to the top