On Sat, 19 Mar 2005 15:25:24 +0100, Thomas Broyer <[EMAIL PROTECTED]> wrote:
> Well actually I was thinking about creating a "unified feed API" (in
> .NET, but could be ported to other languages) and trying to reduce
> memory footprint by reusing Person objects, as well as providing
> relations (
Danny Ayers wrote:
On Sat, 19 Mar 2005 11:55:06 +, Bill de hÓra <[EMAIL PROTECTED]> wrote:
Extend Atom with
FOAF instead if you really need these capabilities in the near term.
Yep, given the timescales involved, that sounds like a good pragmatic solution.
+1, as said in another mail.
Even if A
On Sat, 19 Mar 2005 11:55:06 +, Bill de hÓra <[EMAIL PROTECTED]> wrote:
Extend Atom with
> FOAF instead if you really need these capabilities in the near term.
Yep, given the timescales involved, that sounds like a good pragmatic solution.
Even if Atom doesn't support it, and feeds don't us
Bill de hÓra wrote:
Thomas Broyer wrote:
As I already said, this would greatly help storing feeds efficiently in
databases or object graphs.
Any comment?
-1. The WG shouldn't contemplate standardizing identity management at
this time.
Yes, it could be pinned out until the next Atom version.
This i
Thomas Broyer wrote:
As I already said, this would greatly help storing feeds efficiently in
databases or object graphs.
Any comment?
-1. The WG shouldn't contemplate standardizing identity management at
this time.
This is a complex problem domain, even in closed systems. Feed format
specs are
The use cases are good, and even before you start looking at the
relationship between entries and people there are limits to what you
can do with the author/contributor constructs.
This general issue has had 4+ years of hammering in theory and
practical deployment around FOAF, which is been succe
I like this - even though I disagree with the constraints - as it
follows
nicely on the parallel I developed in the Madonna example [1]
between personal identity and entry identity.
Clearly if the same atom:id were to be used then we are identifying the
id that appears in an entry and the id that
On Friday, March 18, 2005, at 08:23 AM, Thomas Broyer wrote:
I propose adding an optional atom:id element to the Person construct
content model,
If it's not too late, I wouldn't be opposed to this, but I'm not sure I
agree entirely with the specific rules.
with the following rules (to be reworde
Hi there,
It seems something's missing about authors and contributors...
This is allowed:
Thomas Broyer
Thomas Broyer
...
as well as:
Thomas Broyer
Thomas Broyer
or even (less obvious):
Thomas Broyer
Broyer, Thomas
T. Broyer
or
Thomas Broyer
[EMAIL PROTECTED]
Thomas Broyer