[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: to/cc/bcc extension



Aristotle, the email application messed up the markup... it's supposed to be just...

  <to> acct: john.doe @ example.org </to>

(I added some spaces to try to keep the example from being messed up again)

- James

On Mon, Oct 25, 2010 at 12:52 PM, Aristotle Pagaltzis <pagaltzis@xxxxxx> wrote:

* James Snell <jasnell@xxxxxxxxx> [2010-10-15 23:05]:
> Wanted to draw attention to this:
>
>   http://tools.ietf.org/html/draft-norris-atompub-audience-00.html
>
> It introduces to/cc/bcc elements to an Atom entry.
>
>   <entry>
>     ...
>     <to>acct:john.doe@xxxxxxxxxxx <acct%3Ajohn.doe@xxxxxxxxxxx></to>
>     <to>acct:bob@xxxxxxxxxxx <acct%3Abob@xxxxxxxxxxx></to>
>     <cc>acct:jane.doe@xxxxxxxxxxx <acct%3Ajane.doe@xxxxxxxxxxx></cc>
>     <cc>acct:jane@xxxxxxxxxxx <acct%3Ajane@xxxxxxxxxxx></cc>
>     <bcc>acct:jean.deux@xxxxxxxxxxx <acct%3Ajean.deux@xxxxxxxxxxx></bcc>
>     <bcc>acct:max@xxxxxxxxxxx <acct%3Amax@xxxxxxxxxxx></bcc>
>     ...
>   </entry>
>
> Comments are welcomed and requested.

First: your example XML is broken. (Unescaped angle brackets in
content.)

Next: microparsing, and of text content no less (as opposed to
attribute values)? How hideous.

I will suggest something like

   <audience rel="to"
       address="acct:john.doe@xxxxxxxxxxx"
       label="acct:john.doe@xxxxxxxxxxx" />

The label should be optional of course.

Now you have something tractable to XML tools, eg. you can write
reasonable XPath queries across these elements.

Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>