[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [syndication] Re: [DISCUSS] eXtensible Content Syndication (the next step for O CS)
- To: syndication@yahoogroups.com
- Subject: Re: [syndication] Re: [DISCUSS] eXtensible Content Syndication (the next step for O CS)
- From: burton@relativity.yi.org
- Date: 13 Aug 2001 09:30:45 -0700
- In-reply-to: "Duynstee, Teun"'s message of "Mon, 13 Aug 2001 09:29:37 +0200"
- References: <8B6DFE6EBCC6D411B951001083FD745A0F88C9@CREAIMSR01>
- User-agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
"Duynstee, Teun" <teun.duynstee@macaw.nl> writes:
> Three comments:
>
> 1) Lets keep really clear if the attributes on the format element should or
> shouldn't carry a prefix when the XCS namespace is not the default
> namespace.
I don't understand what you mean? You are advocating *not* using attribute
prefixes... right?
> 2) What I would really like in a successor to OCS would be a way to
> deprecate a certain URL. Often, the URLs of feeds change. Of course: rather
> not, but it happens for both logistic reasons (think www.moreover.com ->
> p.moreover.com) and marketing reasons (think egroups.com ->
> yahoogroups.com). Nowadays, aggregators (including end-users of client
> headline viewers) will only notice this situation when:
> a) the feed is discontinued, error message on screen
> b) a second feed with identical content shows up
>
> Maybe we could use something like:
> <format mimeType="" contentType="" location="">
> <deprecated since="" continued-at=""/>
> </format>
>
> or maybe something the other way around, where only the current location
> appears in the list, but carrying a list of previous deprecated locations.
Good idea.
This should be a deprecations module though. We also need an 'until' attribute
which will detail how long the deprecations will remain in effect for.
> 3) I think it is important that XCS consumers can see from the listing which
> feeds are basically the same info, but using a different format. This is a
> very common situation (check out the Moreover OCS).
Yes... but this is already possible with OCS. I want to carry it on into XCS.
> XCS consumers will want to pick their favoured format and use this. Of course,
> this is a non-issue if the format element is intended to occur multiple times
> per feed. Is that indeed the intention?
It is in my mind... ;)
> Would it be usefull then to allow for different languages of the same feed?
Yeah... I don't know about this. I have thought about it and it is generally a
good idea. The only problem here is that it would require one level of
nesting.
I could/would make the argument that almost all multiple language systems use
different URLs for the base.
Something to think about though.
Kevin
- --
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burtonator@acm.org )
Cell: 408-910-6145 URL: http://relativity.yi.org ICQ: 73488596
We can plant a house, we can build a tree
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt
iD8DBQE7eAC1AwM6xb2dfE0RAqbmAJ4jnMidv6yH97Pxi89V6aC+F4CloACgicCo
+kBz7bIkmtgGuPEFnxIitek=
=QB5F
-----END PGP SIGNATURE-----