Re: [syndication] Re: [DISCUSS] eXtensible Content Syndication (the next step for OCS)

[burton@relativity.yi.org]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> I'm stepping into the debate somewhat late, having been on holiday (in sunny
> Scotland)

hope you had fun :)

> It's not complete but here is the current state of my proposal for version 0.5
> of OCS: (There are some typos etc, the main part is the example of a v0.5 OCS
> file)

Cool.. thanks for sharing...

I honestly don't care how this goes but we need to move forward here.  Clearly
there are a lot of problems here and a lot of people want a newer standard.  

> http://internetalchemy.org/ocs/directory-0.5.html

I like your addition of an image but I don't like that it is a fixed size.  I
was going to propose a module dedicated to images which would allow multiple
sizes from icons (16x16 or so) all the way up to larger images and including
"active media" including SMIL an SVG (in the hope that these will be free and
open standards available even Linux geeks like me)

I don't think your 'schema' element is appropriate.  This would imply that OCS
can only syndicate XML.  I think we need a contentModel so that we can use ANY
URI to describe the resource it points to.

As per ocs:updatePeriod.  I wish we could use the 'syndication' module from RSS
1.0.

.... I realize it is just a proposal and I am just trying to be constructive...

> As ever it is purely a proposal, fed by contributions from the syndication
> community. Comment and feedback is very very welcome.

> Highlights are:
<snip>

> Well, OCS is slowly being adopted by content producers and aggregators and
> there are many people and companies who are using the OCS feeds from xmlTree.

>I see OCS as a leveller. By publishing and consuming OCS feeds every aggregator
>ends up with the same channels and services. The differentiation between
>aggregators then moves up a level to value added services, i.e. user
>interfaces, delivery, personalisation, ratings, integration etc.

> There's a need for the producers of content to be paid for their services if
> they desire. I'd like to see the development of a payment module that allows
> producers to label their services with the cost and payment mechanisms
> supported. Purely optional of course but the end user has the right to know
> what to expect.

Hm... maybe I will take a stab at this.  We have the basis for a 'services'
architecture within reptile.  I need to spend more time on this though.  One of
the base services we want is for integration of 'micropayments'.   Right now
there aren't many solutions for this but paypal can be a step in the right
direction.  

> I'd like also to see meta OCS files, i.e. OCS listings of OCS files.  There's
> nothing to stop you doing this in OCS 0.4 of course.

Maybe... 

- -- 
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burtonator@acm.org )
        Cell: 408-910-6145 URL: http://relativity.yi.org ICQ: 73488596 

Never under estimate the power of a hacker!



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt

iD8DBQE7fChVAwM6xb2dfE0RAoGcAKDEqnw3Hkvpsi3ZSnd+2liKgaRwygCfS109
+khrbW56fxwUcsqkC7DstVI=
=8vsZ
-----END PGP SIGNATURE-----