You may extend a resource list with any field you want. The schema is extensible is not fixed. In this respect indeed you will end up with different implementations that store different fields in different ways.
Believe it or not is what vendors pushed IETF to do, so that they can lock in their customers while using the open standards. A practical example. For instance you cannot re-use the contact list built by Eybeam easily in another client. While is possible to export it somehow, the opposite is impossible. A resource list composed by other client that does not have a particular hash value calculated by Eybeam itself will not be loaded by Eyebeam even if the data is compatible with the resource-list format. Adrian On Jul 9, 2009, at 1:34 PM, Iñaki Baz Castillo wrote: > 2009/7/9 Adrian Georgescu <[email protected]>: >> You use this >> >> http://tools.ietf.org/html/rfc4482 > > > This schema only defines the following fields: > > <xs:element name="card" type="xs:anyURI"/> > <xs:element name="display-name" type="xs:string"/> > <xs:element name="homepage" type="xs:anyURI"/> > <xs:element name="icon" type="xs:anyURI"/> > <xs:element name="map" type="xs:anyURI"/> > <xs:element name="sound" type="xs:anyURI"/> > > > These are not enough at all, custom fields as home phone, mobile, > e-mail are missing :( > > > Perhaps an UA could use custom attributes for storing contact data, > but then... => interoperability. > > > -- > Iñaki Baz Castillo > <[email protected]> > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
