2007/5/21, Joe Shaw <<a href="mailto:joe@joeshaw.org">joe@joeshaw.org</a>>:<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hey, On 5/20/07, Mikkel Kamstrup Erlandsen <<a href="mailto:mikkel.kamstrup@gmail.com">mikkel.kamstrup@gmail.com</a>> wrote: > Right. That was not entirely thought through. I must admit that I find > <a href="http://beagle-project.org/Writing_clients">http://beagle-project.org/Writing_clients</a> a bit confusing > though. Ah, I hadn't actually read that page. > As far as I can tell from your words here I gather that Beagles > HitType means "this-is-a" and that the FileType means "this-comes-from", but > that's not how I read that site (fx. Document is a FileType whereas I would > expect it to be a HitType with FileType=File). No, you're getting them backward.  HitType is basically "this comes from" -- hence "File", "Email", "WebHistory" but nothing more specific than that.  FileType is "this is a".  You can think of it basically as more general but in the same idea as a MIME type.  That is, application/pdf and application/msword are both "document". image/jpeg, image/gif, and image/png are all "image".</blockquote><div> Yes, I realised that I got it backwards right after clicking "send"  - where is that spec for the all-encompassing-undo-button? :-) </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> > The Category  is what Beagle calls HitType. (You mean FileType here.)  What is the purpose of having a hierarchy for Category?  What would "File" have that would trickle down to all of "Video", "Document", "Archive", etc.  You had better not say "filename", because email attachments often don't have them. :)</blockquote><div> Right, it might very well be overkill to have a tree structure on the sources. I just figured that since we already have tree structures for defining fields and categories it would only be natural that sources where  defined in a tree too. So this was mostly in the name of coherency than inspired by actual needs :-) Just brainstorming... Evgeny suggested on IRC that the source could be specified in the Category field of an object. The cat field would have to be multivalued so that you could set the cats of an image in a zip-ball to "cat:Image" and "src:Archive". This coupled with a flat structure on the source spec might be what we are after... </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> The Source is where the object originates from, a more general > thing than Beagles FileType. (You mean HitType here.)  This seems reasonable, although "Source" in Beagle means the specific backend which generated it.  But that's just a terminology issue. > Fields are "properties" that are available according to the spec of the > category and the source. Yeah, that makes sense. > Then fx there could be a SourceURI field so that you could determine that a > given image with source=Archive was from a zip file attached to and email... Yep, in Beagle this is called the ParentUri, and that's what gets opened by the UIs.</blockquote><div> Good, I was also trying to keep a bit in the spirit of beagle. </div>Cheers, Mikkel</div>