[Bug 31982] Document client-interests parsably

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=31982

--- Comment #2 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-11-30 02:47:30 PST ---
Having client interests be machine-readable is good, but I'd like a test in
test/test-specparser.py or something. (Does `make check` still pass, btw? I
recently reinstated test-specparser, which wasn't run by `make check` and so
hadn't worked for several releases.)

The syntax I had in mind was that client interests would either look like
interface names (o.fd.T.C.I.MailNotification) or like contact attributes and
other tokens (hypothetically, o.fd.T.C.I.MailNotification/count).

Perhaps rather than having name="" be magical (which makes the short_name be
the empty string, which seems rather astonishing), it'd be better to have
different markup for the two cases, something like this?

   <interface name="o.fd.T.C.I.MailNotification">
     <tp:is-client-interest>
       Clients MUST blah blah unless they enable <tp:token-ref>count</> instead
     </tp:is-client-interest>

     <tp:client-interest name="count">
       Clients MAY blah blah without adding the interface name as an interest
     </tp:client-interest>

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.