[uf-discuss] a question about concatenation and hAtom entry content

Brian Suda brian.suda at gmail.com
Fri Jun 1 07:25:54 PDT 2007

On 6/1/07, David Janes <davidjanes at blogmatrix.com> wrote:
> > --- maybe i mis-interpreted this, but do you mean that in a
> > <p class="entry-content"><strong>Content</strong></p>
> >
> > the <strongs> 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 such that only text is implied?

--- 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 issue? i don't think
the spec should mandate that it NEEDS to be HTML, it should be left
upto the transforming app. It makes complete sense to do so when going
from HTML+hAtom->atom, but not much sense when converting to TXT or
something else.

For instance, in hCalendar there is a NOTES field, the spec doesn't
say what to do with any HTML formatted text and how to style it. X2V
attempts to add some fancy ASCII code around *strong* and others, but
this is above and beyond the spec. This is because the ics file does
not understand HTML mark-up, but maybe google calendars does, so for
another app it makes sense to preserve that HTML mark-up in the NOTES

Maybe there is a way to clarify this on the wiki as some sort of
SHOULD depending on the intended output?


brian suda

More information about the microformats-discuss mailing list