Dear Ryan,
Sorry that my description was not precise enough.
What I want to achieve is: store <actor>, <verb>, <object>, and <target> of an
activity in Shindig and when retrieving the activity get a JSON that delivers
the stored values and in addition includes the title attribute with something
like
{
"language": "en",
"title":"<actor> renamed document <object> into <target>"
}
Shindig should use a lookup table that has a natural language template per
activity verb.
With real data instead of placeholders this would look like
{
"language": "en",
"title": "Peter renamed document 'meeting protocol2.pdf' into 'meeting
protocol for second project review.pdf'"
}
I hope that helps. If not, please try to rephrase what you understood, so that
I can see where exactly the problem with understanding is.
Regards
René
-----Ursprüngliche Nachricht-----
Von: Ryan Baxter [mailto:[email protected]]
Gesendet: Montag, 1. Dezember 2014 17:18
An: [email protected]
Cc: Florian Holzschuher; Christian Ochsenkühn
Betreff: Re: Natural language version of activities in Shindig
Hi Rene,
Can you provide a more concrete example of what you are trying to do?
I am having a hard time grasping your question.
On Mon, Dec 1, 2014 at 7:47 AM, René Peinl <[email protected]> wrote:
> Dear Shindig community,
>
> we are facing a challange in our project, that we are using Shindig to
> collect activities from various systems and want to show activities
> coming from Shindig in every system. Currently Shindig only delivers
> the basic activity data like activity verb, object, target and so on.
> However, we’d like to show a natural language version of the activity
> in the activity stream (full sentence) which includes multi-lingual
> presentation of the contents. An example would be „<actor> has added a
> comment to <object>“ or „<actor> renamed document <object> into
> <target>“. The activitystrea.ms standard specifies the title attribute for
> that purpose.
>
> <http://activitystrea.ms/specs/json/1.0/#activity>
> http://activitystrea.ms/specs/json/1.0/#activity
>
> In Shindig this attribute attribute is present and handled, but only
> in a pass-through manner.
>
>
>
> In order to avoid duplication of code, our natural choice would be to
> extend Shindig to generate the natural language version of the
> activities in the title attribute, if title is not present in the
> database. We would use files for translation and formatting templates
> (only string formatting, not colouring or layout), so that every
> administrator can influence both without any coding.
>
>
>
> Would this be an interesting extension for the Shindig base system and
> do you have any suggestions on how to integrate such an extension from
> an architecture point of view? We are e.g. not sure whether to deliver
> several translation in the same JSON as shown here
>
>
> <http://www.w3.org/TR/2014/WD-activitystreams-core-20141023/#naturalLa
> nguage
> Values>
> http://www.w3.org/TR/2014/WD-activitystreams-core-20141023/#naturalLan
> guageV
> alues
>
> or use a parameter from the client to choose the language.
>
> My guess would be that other people will face similar problems.
>
>
>
> Regards
>
> René
>
>
>
