| [PROJECT] - Phased Adoption Framework [message #99] |
Sat, 09 October 2004 05:38 |
Eclipse User |
|
|
|
Originally posted by: ilias.lazaridis.com
[crossposted, as "eclipse.foundation" is new & unknown]
[followup to eclipse.foundation]
-
The problem:
- Serveral vendors solve a similar problem differently, creating a proprietary standard
- Excessive internal usage of this standard do not allow fast transistion to a formal standard.
- An collaborative project implements a formal standard (or specifies something which should serve as a future [quasi]standard).
- The vendors can adopt this standard in phases.
- They provide "adaptors" and similar constructs, which are provided by a framework.
The "Phased Adoption Framework" (PAF) would provide a foundament for this.
PAF could start as a subproject of the technology project or of the tools project.
Possibly an initial codebase could be extracted due to an refactoring of the relevant TPTP project code. It seems that TPTP has implemented the basic concept of a PAF (although most possibly not for generic reuse).
A release version would be used initially within :
- TPTP
- BIRT
Future eclipse projects with similar standartization problems could immediately rely on a tested framework.
-
To understand more about this project suggestion, the underlying technical and political problems and the PAF usage in TPTP simply review this thread:
Re: Is BIRT good for Eclipse?
http://www.eclipse.org/newsportal/article.php?id=79&grou p=eclipse.birt
..
--
http://lazaridis.com
|
|
|
Powered by
FUDForum. Page generated in 0.05580 seconds
] 
Search
Help
Register
Login
Home
