Hi, Thanks for your quick response. To elaborate my use case a bit more. I want to add todo's on camlistore's content. So when a new mail message is imported in camlistore, I want to 'add' a todo label, that something needs to be done with this item.
So option 2 is a good one, and I think it is a good use case to use claims to add a todoTitle attribute. -- AJ Op donderdag 29 juni 2017 18:04:14 UTC+2 schreef mpl: > > Hi, > > 3 examples of ways you could model that: > > 1) (dumb but easy) > one top permanode, with a text file as a camliContent. > everytime you modify the TODO list, you modify the text file, and you > just change the camliContent value to the hash of the new file > > 2) (a bit smarter, but more book-keeping) > one top permanode. each TODO list item is another permanode referenced > on the top permanode with a camliPath. > each list item permanode has a (text) content field, which is the > acual TODO item (e.g. "do laundry"). > > 3) ask Google to give us an API to Google Keep (lol), and write an > importer for it. > > > > On 29 June 2017 at 16:53, Albert-Jan de Vries <[email protected] > <javascript:>> wrote: > > Hi, > > > > I'm looking at Camlistore to see if it is possible to add Todo's to the > > content that is stored in Camlistore. I'll probably need some kind of > schema > > for this (based on schema.org). So what is a good start for storing > todo > > lists in camlistore? > > > > -- AJ > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Camlistore" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
