| Summary | Add x-vbookmark support |
| Queue | Trean |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | jan (at) horde (dot) org |
| Created | 08/28/2008 (6106 days ago) |
| Due | |
| Updated | 11/13/2011 (4934 days ago) |
| Assigned | |
| Resolved | 11/13/2011 (4934 days ago) |
| Milestone | 2 |
| Patch | No |
State ⇒ Rejected
to be decidedly balkanized on proprietary protocols. Closing...
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Trean
Summary ⇒ Add x-vbookmark support
Type ⇒ Enhancement
State ⇒ Accepted
content type. This seem to be modeled after iCalendar data, so my
guess on a valid bookmark object is:
BEGIN:VBKM
VERSION:1.0
URL:http://www.example.com
TITLE:Url Title
END:VBKM
There is also an unknown X-IRMC-URL property.
There seem to be another object type specified with BEGIN:VENV. Not
sure what it does, but it might be grouping individual bookmarks in a
folder.
To find out the complete syntax, we probably have to add a
synchronization stub that simply accepts any incoming data and logs
it, so that we can further analyze.