karma in API is less granular than karma on the web site

I would like to ditto this request. The particular use I have for this is because I use karma to help highlight bugs from people with high bug karma, since their bug reports tend to be higher quality and thus better correlate to issues that should be investigated. Currently I use the aggregate karma value, but this is not sufficient.

I imagine someone can update the Person to export the attribute

IPerson...
karma_category_caches = exported(
        CollectionField(
            title=_("The caches of karma scores, by karma category"),
            readonly=False, required=False,
            value_type=Reference(schema=IKarmaCache)))

But a lot more work is need to export IKarmaCache which is not Published by Launchpad. There is not infrastructure to support this. This problem is like gpg_keys (which is still broken at the moment) or distribution mirrors. At a minimum, someone must create a safe url to that REST use may be/?

    <browser:url
        for="lp.registry.interfaces.karma.IKarmaCache"
        path_expression="string:+karma-caches/${id}"
        rootsite="api"
        attribute_to_parent="person" />

Then update the interface:
IKarmaCache...
export_as_webservice_entry('karma_cache')...

Then export some or all the of the fields.

I was pointing someone who asked about this to this bug, but I've just noticed it has been marked as invalid without specifying the reason.

What was the rationale for marking it as Invalid?

Thanks.

We have some open questions about karma, but its true - this bug describes a real problem.