Hi Reto,
about hallo editor: the newest version you can find in [1] and is made by
and being driven by Henri and it's MIT licensed. Sinse it's implemented as a
jQuery UI widget it doesn't need VIE to work, you can activate it by using
$("#content").hallo();
But maybe I missed something along the conversation..
about the more direct interaction with enhancements from stanbol you might
be interested in annotate.js [2] with a demo at [3].
As far as I know Sebastian is working on VIE Widgets and also myself when I
find time. My next task will there be building an autocomplete widget which
will use an entityhub query for feeding an autocomplete, e.g. type=Person,
using VIE.
[1] https://github.com/bergie/hallo
[2] https://github.com/szabyg/annotate.js
[3] http://dev.iks-project.eu
Cheers,
Szaby
On 6 October 2011 13:59, Reto Bachmann-Gmür <[email protected]> wrote:
> Hi Sebastian,
>
> A hallo version sounds good.
>
> I've just added a maven folder with a pom.xml to iks/VIE this allows
> to deploy VIE as a maven resource bundle and thus being integrated in
> maven projects without requiring the files to be duplicated (see
>
> https://github.com/retobg/sling-stanbol/blob/master/sling-stanbol-servlet/pom.xml
> to see how the VIE resources can be included in a maven project).
>
> Cheers,
> Reto
>
> On Thu, Oct 6, 2011 at 9:29 AM, Sebastian Germesin
> <[email protected]> wrote:
> > Hi Reto,
> >
> > maybe you can use Szaby's hallo Editor together with the newest version
> of
> > VIE.
> > I suppose that he is currently porting it to the newest version.
> >
> > I have included him in this message, so, let's wait for his answer.
> >
> >
> > Cheers,
> > Sebastian
> > Am 05.10.2011 um 22:05 schrieb Reto Bachmann-Gmür:
> >
> >> Hi Sebastian
> >>
> >> For my integration demos I've integrated the wymwdit branch of VIE I
> >> notice however that this version is much older than the master branch.
> >> Is there a way to use an apache license compatible editor and a recent
> >> version of VIE
> >>
> >> Cheers,
> >> Reto
> >>
> >> On Tue, Oct 4, 2011 at 11:48 AM, Sebastian Germesin
> >> <[email protected]> wrote:
> >>>
> >>> Hi Reto,
> >>>
> >>> Am 30.09.2011 um 08:44 schrieb Reto Bachmann-Gmür:
> >>>
> >>>> Hi Sebstian
> >>>>
> >>>> Thank for the code snipped. I was unaware this functionality was part
> >>>> of VIE (saw something similar in the defunct VIE²) and was assuming
> >>>> that I had to care about implementing the REST calls myself.
> >>>
> >>> Yes, you're right. This is the functionaltity that was in VIE^2 and has
> >>> now enriched VIE. So, the big plus here is, that you should never
> really
> >>> care about doing the calls on your own.
> >>>
> >>>
> >>>> What
> >>>> serialization format is this VIE functionality using for communication
> >>>> with the server, not JSON-LD?
> >>>
> >>> So far, it sends the raw text to the /enhancer URL and the result needs
> >>> to be in "application/rdf+json" format.
> >>>
> >>>>
> >>>> What are / how can I use the entities passes to the callback function?
> >>>
> >>> In principle: Yes.
> >>> The entity is a backbone JS model, which means that you can perform a:
> >>>
> >>> <entity>.get('foaf:name')
> >>>
> >>> to retrieve the foaf:name property of that entity.
> >>> same works with
> >>>
> >>> <entity>.set({"foaf:name" : "Mr. Foo"});
> >>>
> >>> What you might need to do in the first place is a
> >>>
> >>> vie.load({entity: entity})
> >>> .using('stanbol')
> >>> .execute()
> >>> .done(function(x) {})
> >>> .fail(function(f){});
> >>>
> >>> This then loads properties from stanbol for that specific entity into
> the
> >>> memory.
> >>> However, the load/save functionality from stanbol is currently under
> >>> development
> >>> in VIE, so more or less unstable to use. But please provide us with
> >>> feedback
> >>> there.
> >>> For DBPedia entities, you can use the DBPedia service ([1]), to query
> for
> >>> properties
> >>> for an entity. Please have a look at [2], how to use that one...
> >>>
> >>>> Can I get the triples from them and add them to an rdfQuery databank?
> >>>>
> >>>
> >>>
> >>> We decided to not bind the VIE lib too much to other libraries, there
> is
> >>> rdfQuery used as parser/serializer but so far, there is no direct
> >>> transformation
> >>> between a VIE entity and rdfQuery triples.
> >>>
> >>>
> >>> Cheers,
> >>> Sebastian
> >>>
> >>> [1] https://github.com/neogermi/VIE/blob/master/src/service/DBPedia.js
> >>> [2]
> https://github.com/neogermi/VIE/blob/master/test/service/dbpedia.js
> >>>
> >>>> Cheers,
> >>>> Reto
> >>>>
> >>>> On Thu, Sep 29, 2011 at 3:00 PM, Sebastian Germesin
> >>>> <[email protected]> wrote:
> >>>>>
> >>>>> Hi Reto,
> >>>>>
> >>>>> just a short question:
> >>>>>>
> >>>>>> As a next step I would like to integrate VIE in the enhancer
> interface
> >>>>>> so
> >>>>>> that the enhancements appear while you type. VIE could pass its
> >>>>>> content
> >>>>>> as
> >>>>>> JSON-LD with ajax to the server. Is there an existing
> >>>>>> MessageBodyReader
> >>>>>> or
> >>>>>> other JSON-LD parser in use in Stanbol or elsewhere?
> >>>>>>
> >>>>>
> >>>>> I don't understand the information flow here. The user types
> something
> >>>>> into
> >>>>> a text-field. The text gets then send to stanbol using VIE (see code
> >>>>> example)
> >>>>>
> >>>>> var elem = $('<p>This is a small test, where Steve Jobs sings a
> >>>>> song.</p>');
> >>>>> var v = new VIE();
> >>>>>
> >>>>> v
> >>>>> .use(new v.StanbolService({name: 'stanbol', url : "/"}))
> >>>>> .analyze({element: elem})
> >>>>> .using('stanbol')
> >>>>> .execute()
> >>>>> .done(function(entities) {
> >>>>> //Your code goes here
> >>>>> })
> >>>>> .fail(function(f){
> >>>>> //Your error-handling-code goes here
> >>>>> });
> >>>>>
> >>>>> and after that, each returned entity could be presented on the UI.
> >>>>> Where
> >>>>> do
> >>>>> you
> >>>>> want to pass around JSON-LD Objects?
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> Sebastian
> >>>>>
> >>>>>>
> >>>>>> Cheers,
> >>>>>> Reto
> >>>>>
> >>>>> --
> >>>>> M.Sc. Sebastian Germesin
> >>>>> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH (DFKI)
> >>>>>
> >>>>> Stuhlsatzenhausweg 3
> >>>>> 66123 Saarbruecken
> >>>>> Germany
> >>>>>
> >>>>> Tel.: +49.681.85775.5079
> >>>>> Fax.: +49.681.85775.5021
> >>>>>
> >>>>> email: [email protected]
> >>>>> GPG: http://www.dfki.de/~germesin/gpg/germesin_dfki.gpgkey
> >>>>> web: http://www.dfki.de/~germesin
> >>>>> skype: neogermi1337
> >>>>> twitter: germesin
> >>>>> github: http://github.com/neogermi
> >>>>>
> >>>>> ###
> >>>>> #
> >>>>> #
> >>>>>
> >>>>>
> >>>
> >>> --
> >>> M.Sc. Sebastian Germesin
> >>> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH (DFKI)
> >>>
> >>> Stuhlsatzenhausweg 3
> >>> 66123 Saarbruecken
> >>> Germany
> >>>
> >>> Tel.: +49.681.85775.5079
> >>> Fax.: +49.681.85775.5021
> >>>
> >>> email: [email protected]
> >>> GPG: http://www.dfki.de/~germesin/gpg/germesin_dfki.gpgkey
> >>> web: http://www.dfki.de/~germesin
> >>> skype: neogermi1337
> >>> twitter: germesin
> >>> github: http://github.com/neogermi
> >>>
> >>> ###
> >>> #
> >>> #
> >>>
> >>>
> >
> > --
> > M.Sc. Sebastian Germesin
> > Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH (DFKI)
> >
> > Stuhlsatzenhausweg 3
> > 66123 Saarbruecken
> > Germany
> >
> > Tel.: +49.681.85775.5079
> > Fax.: +49.681.85775.5021
> >
> > email: [email protected]
> > GPG: http://www.dfki.de/~germesin/gpg/germesin_dfki.gpgkey
> > web: http://www.dfki.de/~germesin
> > skype: neogermi1337
> > twitter: germesin
> > github: http://github.com/neogermi
> >
> > ###
> > #
> > #
> >
> >
>
