[Syncevolution-issues] [Bug 1368] New: Synthesis extensions X-Synthes-Ref, X-CustomLabel-: enable when not using Evolution backend

http://bugs.meego.com/show_bug.cgi?id=1368 Summary: Synthesis extensions X-Synthes-Ref, X-CustomLabel-: enable when not using Evolution backend Classification: MeeGo Projects Product: SyncEvolution Version: unspecified Platform: Netbook OS/Version: IA Status: ASSIGNED Severity: normal Priority: Medium Component: SyncML AssignedTo: syncevolution-bugs(a)meego.bugs ReportedBy: jingke.zhang(a)intel.com QAContact: jingke.zhang(a)intel.com CC: syncevolution-bugs(a)meego.bugs, syncevolution-syncml-bugs(a)meego.bugs Estimated Hours: 0.0 This is from http://bugzilla.moblin.org/show_bug.cgi?id=10462 Description From pohly 2010-04-04 12:48:57 PST (-) [reply] Steps to reproduce: - sync Synthesis iPhone client, SyncEvolution server, Evolution - modify contact on iPhone - send to server and Evolution - TYPE="X-Synthesis-Ref0" is added to ADR, EMAIL, TEL Outcome: - Evolution shows email as "other" (might be right, there was no TYPE=HOME/WORK) - ADR is not shown (NOT right!) Our XML configuration contains the TYPE=X-Synthesis-x extensions. We inherited those from the Synthesis example config. Having them is useful when operating as server with the file backend, because the iPhone client can store and later retrieve its extensions. But when storing an item in Evolution, we should not add these extensions. Implementing that is tricky, because we don't want to maintain two different sets of vcard profiles. Not sure how to do this yet. ------- Comment #1 From pohly 2010-04-09 09:22:38 PST (-) [reply] ------- As a short term solution I disabled the extensions in the config. Now we can treat this issue as an enhancement request. Here's an idea I had. We could add a new "static-rule" XML parameter with the following semantic: - can appear in any XML element - value are boolean expressions with ! | & and brackets, with plain words as atoms, for example: KDE | !EVOLUTION - a backend can produce new profiles by giving the original profile ("vCard"), the new name ("vCard-Evolution:") and which atoms are to be set (EVOLUTION) - an XML parser does that by iterating over all elements and removing those for which "static-rule" is false - we must remove the parameter in the config passed to the engine or extend the engine to ignore it ------- Comment #2 From pohly 2010-04-20 05:38:07 PST (-) [reply] ------- Lukas explained this in an email: X-Synthesis-RefX was introduced a while ago for the Windows Mobile clients as a handle for servers to keep multiple TELs, ADRs, URLs, EMAILs of the same TYPE apart. As Windows Mobile has fixed fields (and no dynamically expandable arrays like iPhone or Symbian), the RefX are just hard-wired enumerations of equally typed fields, like HOME 1, HOME 2 etc. This is something we added mainly for Oracle as they wanted control of which TEL goes to what field. On the iPhone, multiple occurrences of ADR/TEL/URL/EMAIL are dynamic, but have a persistent ID (not just an index) that allows referencing them later. So I exposed them using the already introduced X-Synthesis-RefX syntax. Having these IDs allows full fine grain control over what gets updated, but a full blown server side implementation for this would need a per-device mapping table. With a server that just stores the X-properties along with the data it works as well, however only as long only one device is synced (Oracle does neither). This is iPhone only (so far), and exposes the custom labels (which don't map to a TYPE). We don't have a full implementation (with the per-device ID mapping) in the server (altough it would be possible with some extra scripting). The IOT server on www.synthesis.ch just stores custom labels, if present, along with the TEL/EMAIL/ADR/URL, but ignores the X-Synthesis-RefX. -- Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug.