[XESAM] RC1 out

[Mikkel Kamstrup Erlandsen]

Hi all,

As the subject says, XESAM RC1 is out, much later than I had hoped, but well
- if you want the bad excuses read my blog. Let me talk a little before I
give you the link to the spec.

As you may know we have an age old project request[1] up on FDO bugzilla.
This plus the horribly slow wiki hosted at FDO finally drove me to set up
our own wiki at http://xesam.org. All the FDO XESAM pages has been
DEPRECATED.

Let me stress that we are still a FDO project, our wiki is just hosted
elsewhere (and maybe primary mailing list in the future). I'm sorry for
those of you who will have to have "yet another wiki account".

That aside: http://xesam.org/main/Xesam90 is what you want to look at. There
are compiled PDF versions of the spec and onto there too (huzza for docbook
export (which the FDO wiki doesn't have)).

Please comment here or on #xesam at FreeNode.

CHANGELOG:
It is a bit bigger than I had hoped, but here goes...

 User Search Language
 * Keywords to fields map defined
 * Type selector defined to search both source and content types
 * PUNT: Unit system ie, fx no 1KB, you must write 1024

Query Language
 * Rename "type" selector to "category" and change its attributes to
"content" and "source" as the query element attrs.
 * Rename "storedAs" attr on query element to "source"
 * Add element def for userQuery element

Search API
 * Return type for GetHits and GetHitData remains "aav" (not really a
change)
 * Default values for unset fields defined
 * Allow to return almost arbitrary types for fields - ie does not have to
match the one speciified by the onto, just convert cleanly
 * Define in what cases dbus errors should be returned
 * Rename session prop vendor.ontology.storages to vendor.ontology.sources

Versioned
 * This state of the xesam specification is versioned (0.9), which means
that you can actually use it. Implementations should report the
vendor.xesamproperty 90.

PUNTED:
 * The UI API
 * (controversial) Ontology format. There is no need to specify it for 1.0.
3rd parties would still need to do a lot of engine-specific stuff to use
custom extractors anyway. Perhaps 1.1, maybe first at 2.0.



Cheers,
Mikkel


[1]: https://bugs.freedesktop.org/show_bug.cgi?id=10114 (I should probably
close it now that I've given up)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freedesktop.org/archives/xdg/attachments/20071023/62451d9e/attachment.htm