[Telepathy] ANNOUNCE: telepathy-spec 0.17.17

[Simon McVittie]

I've uploaded telepathy-spec 0.17.17, the "why is ³ a NameChar, but not ²?"
release.

The current development version of telepathy-spec is available as HTML:
  <http://telepathy.freedesktop.org/spec.html>
or from the 'master' branch in the git repository:
  <git://git.collabora.co.uk/git/telepathy-spec.git>
  <git+ssh://git.collabora.co.uk/git/telepathy-spec.git> (for committers)
  <http://git.collabora.co.uk/?p=telepathy-spec.git> (gitweb)

For packagers (e.g. http://packages.debian.org/telepathy-spec):
tar: http://telepathy.freedesktop.org/releases/telepathy-spec/telepathy-spec-0.17.17.tar.gz
sig: http://telepathy.freedesktop.org/releases/telepathy-spec/telepathy-spec-0.17.17.tar.gz.asc

telepathy-spec 0.17.17 (2009-01-06)
===================================

New API:

* Added Handle_Identifier_Map, an a{us} mapping handles to identifiers, and
  a "contact-ids" detail of that type in the MembersChangedDetailed signal
  (for round-trip reduction)

* In the Messages interface, Message_Part_Index and Message_Part_Content_Map
  now have explicit types

* RequestHandles can now raise NotImplemented

Spec markup enhancements:

* Container types have an array-depth attribute indicating how deeply nested
  an array of arrays ... of the type can sensibly be; the only use so far
  is Message_Part, which can have an array depth of 2 (Message_Part[][])

Clarifications:

* The Requested property MUST NOT be accepted by CreateChannel, EnsureChannel
  (it would make no sense)

* The Members_Changed_Detailed flag on groups MUST NOT change during the
  channel's lifetime

* clarify the role of the Display_Name parameter to
  AccountManager.CreateAccount

Regards,
    Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 155 bytes
Desc: Digital signature
Url : http://lists.freedesktop.org/archives/telepathy/attachments/20090106/4dd2fb07/attachment.pgp