Skip to Content.
Sympa Menu

notify-dpml - svn commit: r2034 - in development/planet/services: . draft draft/abandoned recommended standard unsupported

notify-dpml AT lists.ibiblio.org

Subject: DPML Notify

List archive

Chronological Thread  
  • From: niclas AT hedhman.org
  • To: notify-dpml AT lists.ibiblio.org
  • Subject: svn commit: r2034 - in development/planet/services: . draft draft/abandoned recommended standard unsupported
  • Date: Fri, 11 Mar 2005 13:45:12 -0500

Author: niclas AT hedhman.org
Date: Fri Mar 11 13:45:12 2005
New Revision: 2034

Added:
development/planet/services/
development/planet/services/README.txt (contents, props changed)
development/planet/services/draft/
development/planet/services/draft/abandoned/
development/planet/services/recommended/
development/planet/services/standard/
development/planet/services/unsupported/
Log:
Structure for services in planet.

Added: development/planet/services/README.txt
==============================================================================
--- (empty file)
+++ development/planet/services/README.txt Fri Mar 11 13:45:12 2005
@@ -0,0 +1,58 @@
+
+Planet Services
+===============
+
+The Services defined here are is categorized according to the
+support level available on the service.
+
+ draft - The service interface and semantics are not yet fully
stablized.
+
+ recommended - The service interface and semantics have been verified
workable
+ through at least one reference implementation. Recommendation
+ can be issued when several independent community members are
+ backing the service.
+
+ standard - A service that has been fully endorsed by the community. It
+ typically involves more than one implementation, and fully
+ backed by a majority of the active DPML community.
+
+ unsupported - A service interface and semantics that are available on a
+ "as-is" basis. No strong community around it, but at least
one
+ implementation(s) exists. This is typically one-man shows
that
+ has not managed to attract a larger community.
+
+
+Services requires stability, and any changes made to the service (after the
+draft period) MUST result in a new "generation", i.e. different name and
+different package names. We therefor recommend that the package names are
+initially populated with the generation marker, for instance;
+ package net.dpml.console.gen1;
+
+This will ensure that there is no future problems with conflicting service
+interface names.
+
+The project structure should also follow that pattern;
+
+ draft/
+ console/
+ gen1/
+ src/
+ gen2/
+ src/
+
+and so on.
+
+Projects in draft/ that 'dies' should be moved to draft/abandoned/. Community
+members will do so if there is no activity for 6-12 months or so, and the
draft
+is not ready to be published.
+
+
+On top of one or more service interfaces, each Service MUST have well
documented
+semantics of all behaviour, both from the service implementation's point of
view
+as well as from the point of view of the client. Many clients should not
need to
+know anything about the implementation that it will be used against.
+Compatibility test kit for implementations is recommended, but not required.
+
+
+Thank you for your co-operation.
+Digital Product Meta Library, 2005.
\ No newline at end of file



  • svn commit: r2034 - in development/planet/services: . draft draft/abandoned recommended standard unsupported, niclas, 03/11/2005

Archive powered by MHonArc 2.6.24.

Top of Page