Re: [Ekiga-devel-list] Looking for resource-lists documents

[Julien Puydt <jpuydt free fr>]

Julien Puydt a écrit :
> (2) I have seen only a document created by eyebeam (and we're already 
> only partially compatible...).

Ok, here is an example of what I am looking for -- this is a 
resource-lists as made by eyebeam :
<resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists"
		xmlns:cp="counterpath:properties">
	<list name="Contact List">
		<cp:prop name="category" value="Friends" />
		<cp:prop name="category#2" value="Home" />
		<cp:prop name="category#3" value="Work" />
		<entry uri="sip:xlite 192 168 0 12">
			<display-name>xlite</display-name>
			<cp:prop name="given_name" value="xlite" />
			<cp:prop name="pres_subscription" value="true"/>
			<cp:prop name="default_address"
				 value="sip:xlite 192 168 0 12" />
			<cp:prop name="default_address_type"
				 value="sip" />
			<cp:prop name="sip_address"
				 value="sip:xlite 192 168 0 12" />
			<cp:prop name="category" value="Work" />
			<cp:prop name="entry_id"
			value="DF130F538DB74DF68A37AB3CBC9515D8" />
			<cp:prop name="data_hash"
		value="bb9cc5eb7602f9e9adb8350becf82c852b66a50a" />
		</entry>
	</list>
</resource-lists>


All the "cp:" thingies are eyebeam-specific things. That means that 
ekiga will parse the previous and only see :
<resource-lists>
	<list name="Contact List">
		<entry uri="sip:xlite 198 168 0 12>
			<display-name>xlite</display-name>
		</entry>
	</list>
</resource-lists>

and since the <list> element doesn't have a <display-name> child, ekiga 
will display it as :
v List #1
  xlite

ie: you'll see the only entry as its display-name, and the list as "List 
#1".

Comments are welcome -- and examples from other sources even more so!

Snark