I suppose I don't disagree with Maciej's point, but primarily take
umbrage with the seemingly "random" classes that were going to be used
as predefined values. "Copyright" was the biggest offender -- and a
symptom of fflawed thinking -- given the established and widely used
rel-license microformat
On Jun 1, 2007, at 10:59 AM, David Janes wrote:
I concur. Time to start ramping up for hAtom 0.2, if I can get some
blocks of free time.
I'm more than willing to help. I have time to spend on it right now.
I'll work on collecting issues to deal with.
-ryan
__
There has been some previous discussion[1] of this (in 2005!), but it
seems to have been lost.
I think we should use rel-tag tagspaces for atom category schemes.
For those not familiar with Atom, category elements define 3
attributes: term, label and scheme.
hAtom currently defines mapping
On 6/1/07, Ryan King <[EMAIL PROTECTED]> wrote:
On May 31, 2007, at 11:29 AM, David Janes wrote:
> On 5/31/07, Ryan King <[EMAIL PROTECTED]> wrote:
>
>> Another option is that entry content is:
>>
>> Content
>> More Content
>>
>>
>> Is there a reason why hAtom as currently spec'ed only does text
On May 31, 2007, at 11:29 AM, David Janes wrote:
On 5/31/07, Ryan King <[EMAIL PROTECTED]> wrote:
Another option is that entry content is:
Content
More Content
Is there a reason why hAtom as currently spec'ed only does text, not
markup?
I thought it did markup! I totally see what you are
On Jun 1, 2007, at 7:25 AM, Brian Suda wrote:
On 6/1/07, David Janes <[EMAIL PROTECTED]> wrote:
> --- maybe i mis-interpreted this, but do you mean that in a
> Content
>
> the should be carried through? or converted to *Content*?
The strongs (i.e., and all other HTML) should be carried throug
On 6/1/07, Brian Suda <[EMAIL PROTECTED]> wrote:
--- maybe that is a good thing, if i am converting hFeed into
something that is NOT html, say MySQL statements, or a simple CSV
list. Should it have the HTML mark-up or should the app be allowed it
to be 'down-cast' to simple ASCII? is this a spec
On 6/1/07, David Janes <[EMAIL PROTECTED]> wrote:
> --- maybe i mis-interpreted this, but do you mean that in a
> Content
>
> the should be carried through? or converted to *Content*?
The strongs (i.e., and all other HTML) should be carried through.
Interesting -- are people reading the spec s
On 6/1/07, Brian Suda <[EMAIL PROTECTED]> wrote:
On 5/31/07, David Janes <[EMAIL PROTECTED]> wrote:
> I thought it did markup! I totally see what you are saying here
> though; the question here is whether we include the DOM nodes that
> specify entry-content. This isn't in the spec, and you would
On 5/31/07, David Janes <[EMAIL PROTECTED]> wrote:
I thought it did markup! I totally see what you are saying here
though; the question here is whether we include the DOM nodes that
specify entry-content. This isn't in the spec, and you wouldn't want
to do it everywhere (entry-title, for example)
10 matches
Mail list logo
