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
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
I noticed another bug in the RNG. The collected RNG is missing a '?'
after atomIcon:
atomSourceFeed =
element atom:source-feed {
atomCommonAttributes,
( atomTitle
atomUpdated
atomLink+
atomIcon
should be:
atomSourceFeed =
element
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
In other words, the presence of an element with the namespace IRI
http://www.w3.org/2000/09/xmldsig#;
Namespace IRI, is that a find-replace-o?
--
Dave
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 use
David Powell wrote:
Two more things I've just noticed:
PersonConstructs aren't currently allowing extension elements.
anyForeignAttribute and anyForeignElement are currently not
used anywhere.
Proposal for test procedure:
- please publish an updated RNC file somewhere (on atomsub.org?)
- those who
Graham wrote:
Every single Atom keyword apart from this new one is a single
non-hyphenated word. This one sticks out horribly.
Proposal:
Rename atom:source-feed to atom:source
Sounds good to me. I picked PubSub's deployed name for clarity, and to
avoid confusion with the atom:source element we
David Powell wrote:
PersonConstructs aren't currently allowing extension elements.
anyForeignAttribute and anyForeignElement are currently not
used anywhere.
The second point reflects a problem with the draft. I noticed this while
writing it, but figured the WG needed to spot it.
The
+1 to the just pick something and ship it position
On Mar 18, 2005, at 2:44 AM, Dan Brickley wrote:
* Bjoern Hoehrmann [EMAIL PROTECTED] [2005-03-18 11:13+0100]
* Tim Bray wrote:
There are a couple of places where we use uri in the markup,
specifically the atom:uri element (3.2.2) and the uri
10 matches
Mail list logo
