--- Begin Message ---
|
Subject: |
Common Atom Constructs . |
|
Date: |
Tue, 26 Jun 2007 16:58:05 +0400 |
|
User-agent: |
Thunderbird 1.5.0.12 (Windows/20070509) |
SREA Takes Investors For Second Climb! UP 40%.
Score One Inc. (SREA)
$0.42 UP 40%
SREA continues another huge climb this week after hot news was released
Friday. BusinessNewsNow.us has released SREA as featured StockWatch.
This one is still cooking. Go read the news and get on SREA Tuesday!
Already, the first real mashup of this data has been built. Note that
this means the most recently updated entries are returned first in the
feed.
In other words, when you think of the entire application "stack,"
standard protocols had really only worked themselves into the very
bottom.
We use TrackBack here to track who links to SiliconBeat.
With wikis, you can simply go in and fix it and the original
collaborators will probably get notified of the change. Talk about
accountability!
These challenges do not affect Six Apart alone, but the blogging
industry at large. Atom Processors that display the content MAY use the
markup to aid in displaying it.
Thanks to Niall for linking me to it.
HTML and XHTML Content . The language context is only significant for
elements and attributes declared to be "Language- Sensitive" by this
specification.
Atom Documents This specification describes two kinds of Atom Documents:
Atom Feed Documents and Atom Entry Documents. Their goal: set the data
free.
o atom:feed elements MUST NOT contain more than one atom:icon element.
The atom:generator element MAY have a "version" attribute that indicates
the version of the generating agent. o atom:feed elements MUST contain
exactly one atom:title element. The "atom:category" Element The
"atom:category" element conveys information about a category associated
with an entry or feed. The "atom:contributor" Element The
"atom:contributor" element is a Person construct that indicates a person
or other entity who contributed to the entry or feed. If we assume that
we will generate the feeds with a fixed number of entries per feed, then
we need a way to query with a size and offset from the beginning of the
list. Spanning Sync has been recognized by Google as a shining example
of the type of software springing up around their online applications
and Charlie talks about how they plan to keep it that way. The best a
computer can do with it is hope to render it for a human to interpret.
The "atom:uri" Element The "atom:uri" element's content conveys an IRI
associated with the person.
Atom Processors MAY use the IRI to retrieve the content and MAY choose
to ignore remote content or to present it in a different manner than
local content.
Therefore, Six Apart is beginning the process of submitting TrackBack to
the Internet community and establishing TrackBack as a standard.
But being able to do so with impunity is always at risk. Text Constructs
A Text construct contains human-readable text, usually in small
quantities.
The "atom:name" Element The "atom:name" element's content conveys a
human-readable name for the person.
The idea of URI Templates isn't new; I provided code for how to handle
URI Template variable expansion in "Constructing or Traversing URIs? If
you get a "sorry you are banned" message - that is a mistake.
Note that there MUST NOT be any white space in a Date construct or in
any IRI.
Perhaps you missed it earlier, but I mentioned the idea of informal
collaboration.
Syndicating rich search content is an entirely different thing, and that
requires a non-lossy syndication format. The "type" Attribute .
So, here's a question.
o For schemes that define a default authority, use an empty authority
if the default is desired.
The "atom:content" Element The "atom:content" element either contains or
links to the content of the entry.
One typical behavior would be to display only the entry with the latest
atom:updated timestamp.
Businesses will do well the heed the lessons being taught by people like
Dave Winer and Robert Scoble. Email is a great example.
You can digg this post.
Put another way, an atom:id element pertains to all instantiations of a
particular Atom entry or feed; revisions retain the same content in
their atom:id elements.
I will save the rest of the technical details of the Store class for
another day.
But being able to do so with impunity is always at risk.
o atom:entry elements MUST NOT contain more than one atom:rights
element.
Because of its very simplicity there is some vagueness that allows it to
be subject to a dozen little misinterpretations.
I see the new intranet, the new protocol of which is RSS. Not a bad
start, but well below the level of service that having government data
available in workable formats would enable. If you get a "sorry you are
banned" message - that is a mistake.
--- End Message ---
--- Begin Message ---
|
Subject: |
confirm 0cd878f3dcc930349d4528c3a4b71ee8a981d128 |
If you reply to this message, keeping the Subject: header intact,
Mailman will discard the held message. Do this if the message is
spam. If you reply to this message and include an Approved: header
with the list password in it, the message will be approved for posting
to the list. The Approved: header can also appear in the first line
of the body of the reply.
--- End Message ---