Ticket #321 (new enhancement)

Opened 2 years ago

Last modified 6 months ago

Handle nested vCards in AGENT field

Reported by: twogood Assigned to: dgollub
Priority: high Milestone:
Component: OpenSync Version: 0.31
Severity: critical Keywords:
Cc:

Description

The patch from ticket #221 allows the AGENT contents to be converted verbatim to and from XML, but as the AGENT field may contain a nested vCard. (See "3.5.4 AGENT Type Definition" in RFC 2426 for details.) If that vCard is not also converted to and from XML, the idea of representing vCards in XML is not fully implemented.

Change History

08/31/06 20:07:21 changed by twogood

  • type changed from defect to enhancement.

09/07/06 18:46:40 changed by abauer

  • status changed from new to assigned.
  • version changed from 0.X to 0.30.

02/14/07 23:15:15 changed by dfriedrich

  • version changed from 0.30 to 0.31.

10/15/07 23:35:17 changed by dgollub

  • owner changed from abauer to dgollub.
  • priority changed from normal to high.
  • status changed from assigned to new.
  • severity changed from normal to critical.
  • milestone set to OpenSync 0.40.

Any idea how handle nested entries in XMLFormat-*? Should we just dump the nested entry untouched in a xml node/attribute?

I doubt there is any format beside vcard which supports nested entries. But maybe we there are other fields which needs some recursion?

Something for 0.40?

01/20/08 20:38:58 changed by dgollub

  • milestone deleted.

Nothing for 0.40