[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[kNews] New trials: Commerce, Catalogue, Rules, Interface...
- To: kNews
- Subject: [kNews] New trials: Commerce, Catalogue, Rules, Interface...
- From: kNews <k-news@xxxxxxxxxxxxx>
- Date: Wed, 28 May 2003 11:41:21 +0100
Dear All,
An update and road map for you... Lots going on...
1. Introduction
2. Commerce Trial overview
3. Catalogue Trial overview
4. Rules Trial overview
5. Interface Trial overview
6. kendraTools and kendraBase: collaborative software development
7. License Of Responsibility: free (open source) software license
8. How you can help: spread the word
1. Introduction
As you know we are building an open platform for content distribution. We
are soft launching our new Commerce, Catalogue, Rules and Interface trials
over the next few months and will be targeting specific groups during this
period to drive participation. Here is a brief idea of what to expect...
2. Commerce Trial overview
The Kendra Commerce Trial will seek to drive interoperability between
different payment service providers and subscription service providers.
We'll be calling on banks, payment providers, electronic cash providers and
subscription providers to discuss how they can bring about interoperability
by defining their common business practices. For examples: As a content
consumer I want to be able to use one payment system and don't want to have
to sign up to a new subscription just because I'm using a new application
or visiting a new website to get my content. As a content owner/aggregator
I want to be able to provide the most convenient way for consumers to pay
for my content. See:
http://www.kendra.org.uk/commerce.php
3. Catalogue Trial overview
The Kendra Catalogue Trial will seek to drive interoperability between
media catalogue owners or their representatives. We'll be calling on
content owners and aggregators, record labels and independent artists,
motion picture distributors and independent film makers to discuss how they
can bring about interoperability by defining their common business
practices. For examples: As a content consumer I want to be able to get all
my content in one place and don't want to have to go trawling through 100s
of websites/applications looking for that elusive track/movie. As a content
owner/aggregator I want to be able to provide the most convenient way for
consumers to get my content. See:
http://www.kendra.org.uk/catalogue.php
4. Rules Trial overview
The Kendra Rules Trial will seek to enable both the content owner and the
content consumer to state the rules under which they wish to deliver and
receive their content respectively. Well be looking into the codifying of
business practices enabling content owners and the content consumers to
contract only if their rules/criteria match. For examples: As a content
consumer I want to be able to get all my content for a subscription fee of
20 quid per month. As a content owner/aggregator I want to be able to sell
my content on a pay-to-own basis. See:
http://www.kendra.org.uk/rules.php
5. Interface Trial overview
The Kendra Interface Trial will call upon software interface designers
(applications and websites) and consumers to discuss requirements for
interfacing to kendraSystem. For examples: As a content consumer I want any
application or web portal to act as my global view of world content. See:
http://www.kendra.org.uk/interface.php
6. kendraTools and kendraBase: collaborative software development
It's fascinating watching ideas develop for kendraTools - our very own
collaborative design tools. We're taking a very fresh approach of enabling
users to talk (describe objects in their world) in their own language using
their own terminology rather than having to adhere to a specific format or
schema. To build structure we'll then enable the creation of relationships
between these objects.
Nobody likes to be told how to speak or what words to use. In fact we just
can't help making up new ones all the time. And we really like to talk
about ourselves in our own language and terminology. It really seems like a
"bottom up" approach. Perhaps we'll meet the "top down" applications half
way!
And, yes, we're still looking to hire imaginative developers so, if you are
one, take a look at:
http://www.kendra.org.uk/develop.php
7. License Of Responsibility: free (open source) software license
It seems right that Kendra should have it's very own software license.
Seeing as our aim is to make kendraSystem as widely used as possible our
aim with the software license is to reduce all hindrances to participation
to as little as possible. Hence, our license will place no
requirements/restrictions on the user and will explain the reasons for do
this. For more information see:
http://www.kendra.org.uk/lists/archive/k-developers/msg00100.html
8. How you can help: spread the word
kendraSystem will only be created if we all *will* it to happen. Remember
that Kendra's remit is to build a *working* system. Defining a
language/protocol and applications/tools may be necessary to build this
system but without people actually participating it will not be a *working*
system. People and technology go hand in hand. Step by step. "Kaizen", as
Andi says.
So, pass this email on to other people that you think may be interested in
helping create this system. Or you can invite them here:
http://www.kendra.org.uk/profile.php#enroll
And, if you haven't done so already, list yourself on the website by
filling in your details here:
http://www.kendra.org.uk/profile.php#contact
There is no contract with Kendra. There is no obligation other than your
own desire. You can pull out at any time.
And so, we go on... ;-)
Cheers Daniel
- This message was sent to 1575 people.