[okfn-discuss] OSSD and Service Orientation

[John Bywater]

Rufus Pollock wrote:
> 2009/5/21 John Bywater <john.bywater at appropriatesoftware.net>:
>> Also, whilst I remember, there appears to be an aspect that is entirely
>> missing: requiring that all open software service dependencies are also
>> open software services. Dependency services appear not to be mentioned.
> 
> No this is not mentioned because there never seemed to be a consensus
> position on this! It was discussed extensively, see e.g.:
> 
> <http://lists.okfn.org/pipermail/okfn-discuss/2007-August/000498.html>
> 

Thanks, I thought it had been raised somewhere! I guess both options
have their uses, but it's a question of what does each allow - what is
an open software service for?

Of course, being free/open is often considered as an end in itself. But
apparently that's not a consideration sufficient to decide this matter
in a non-arbitrary manner.

Perhaps it would help to think about which needs/desires are realised by
the open aspects of open software services?

>From the POV of Service Orientation the question is very simple: what
sort of service would require another service to be an open software
service?

If the answer is: a replica/derivative service, then we need 'strong' OSSD.

I can't think of what a 'weak' OSSD would support, except curiosity. As
software services are increasingly refactored into service dependencies,
most of a service will be implemented within its dependencies. So 'weak'
will over time tend to become 'almost entirely closed'.

Beyond replication, it would be useful to list some of the different
types of usage of an open software service, as defined by the OSSD.

But what is the OSSD actually for? (And is anybody currently using it?)

John.