On 1/6/07, Danny Angus <[EMAIL PROTECTED]> wrote:
On 1/6/07, Serge Knystautas <[EMAIL PROTECTED]> wrote:
> On 1/6/07, robert burrell donkin <[EMAIL PROTECTED]> wrote:
> > sorting isn't good enough for me either: emails need to be tagged with
> > meta-data on the server. meta-data can then used to present a folder
> > based view to a client or for any other purposes. i think that a rules
> > engine plus a domain specific language would work better than SLIEVE.
>
> Robert,
>
> I'm right there with you. I don't know if GMail has it perfect, but I
> find tagging and better searching much more powerful than the
> foldering system I have from 10 years of emails in IMAP.
>
> Do you see any way to backfit tagging concepts into IMAP, or do we
> need a separate protocol (perhaps http/restful as you say)?
Couldn't you just use metadata to present a view of the mail as if it
was in a folder structure?
I mean, the idea of "moving" mail into folders is really only a UI
metaphor when the mail is in a db, there's no earthy reason why the
underlying storage has to be structured in the way the view presents
it as long as the two things are compatible.
+1
URIs would still be useful, though
i've started to become interested in ideas around the semantic web:
subject-predicate-object is a natural approach to meta-data that can
be run in a rules engine. the email is the subject. headers seem to me
to be predicate-object structured. so i think that there's a natural
mapping somewhere in there (but i'm struggling to comprehend it)
advanced email servers end up assigning ids to emails. these may be
better recast as urls for the client perspective. for example,
imap://server/3453452345
http://server/email/mail3453452345
Desiging a metadata model that supported the creation of hierarchical
views as well as more straightforward uses could be interesting.
+1
:-)
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
