Ticket #321 (new enhancement)

Opened 8 years ago

Last modified 6 years ago

Handle nested vCards in AGENT field

Reported by: twogood Owned by: dgollub
Priority: normal Milestone: OpenSync 0.42
Component: OpenSync Version: 0.38
Severity: normal Keywords:


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

comment:1 Changed 8 years ago by twogood

  • Type changed from defect to enhancement

comment:2 Changed 8 years ago by abauer

  • Status changed from new to assigned
  • Version changed from 0.X to 0.30

comment:3 Changed 7 years ago by dfriedrich

  • Version changed from 0.30 to 0.31

comment:6 Changed 7 years ago 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?

comment:7 Changed 7 years ago by dgollub

  • Milestone OpenSync 0.40 deleted

Nothing for 0.40

comment:8 Changed 6 years ago by tuju

  • Milestone set to 0.42

comment:9 Changed 6 years ago by tuju

  • Priority changed from high to normal
  • Version changed from 0.31 to 0.38
  • Severity changed from critical to normal

i've a feeling that this is still valid for 0.38.

Note: See TracTickets for help on using tickets.