Notifications specification: proposed capabilities

[Quentin Glidic]

Hello,

I’m implementing the notifications specification in my software eventd
(http://www.eventd.org/) for some time now, using a vendor capability
"x-eventd-overlay-icon". I also use the "image/svg+xml" one that
notify-osd adverts too.

The former is about the use of both the icon and the image if provided.
In the current spec, implementations are free to use both, and clients
are free to provide both.
The point of this capability is to let clients know that both will be
displayed, so they don’t have to chose (e.g. some client might find the
icon more important, but having some bonus information to put in the
image, which would make the server ignore the icon if it can’t display
both).
The name comes from the ability to draw the icon overlaying the image. I
got different layouts now and I didn’t change the name. A better one may
be "image-and-icon" or anything someone could come up with.

The latter is about supporting the SVG format for icons. It sounds
interesting to me since most raster formats are likely to be supported,
while vector ones are less common.
It does not strictly respect the spec since it uses "/" and "+", so we
may need some other name, or maybe say that MIME types are accepted as
capabilities.

Cheers,

-- 

Quentin “Sardem FF7” Glidic