Joan, you could try ZKOSS also, I wouldn't mind using widgets to increase productivity, but I think you'll have difficulties connecting the RDF code to them in a generic way. And if not, you will be building a tool, not a platform.
Graphity does not include non-generic code. linkeddata.dk is just one instance running/extending the platform, the codebases are separate. There I use Google Chart Tools (https://developers.google.com/chart/), for example: http://linkeddata.dk/queries/world-bank/denmark/gdp-vs-household Martynas On Mon, Jun 25, 2012 at 10:22 PM, Joan Iglesias <[email protected]> wrote: > > Martynas, > > Ok I see. But your platform allows the possibility of adding plug-ins in a > Eclipse way? Just specifying the url of the provider? > > If I understood well, if I use your platform I could define something similar > to what I wanted to do. I suppose that for each plug-in I have to make a king > of package, with my php code for controllers, XSLT, and so on... I'm right? > How easy is to define a plug-in for your platform? > > Yes you are right, it's not standard technology ZKOSS, but its presentation > layer it's very dynamic and powerful. > > Maybe it could be a good starting point to start defining jena plug-ins for > your platform. But your platform should allow the user the installation in > one click fashion, and the customization of the plug-in using web interface. > It could be possible? > > Nowadays, I think it's not enough XHTML. For some functionality, it's needed > more dynamic contents generation. Maybe your platform could allow the > definition of the view with dojotoolkit? > > ZK and other frameworks I have in mind could allow to define a very dynamic > view generation, and that also means that more types of plug-ins and > utilities can e developed. XHTML in some cases can be limited. > > Best regards > > Joan > >> Date: Mon, 25 Jun 2012 21:41:19 +0200 >> Subject: Re: Planning for a new framework for Jena >> From: [email protected] >> To: [email protected] >> >> Joan, >> >> Graphity also allows defining XHTML templates, so the layout and >> functionallity is fully customizable. You can include all the >> libraries you want, but the platform doesn't deal with client-side >> much -- linkeddata.dk is just one of the possible layouts. >> >> Do you mean http://www.zkoss.org? If I get the concept right, you will >> end up doing the same thing -- writing templates, only in ZK custom >> template language instead of standard XSLT, and probably some provider >> Java code? >> >> Martynas >> >> On Mon, Jun 25, 2012 at 9:16 PM, Joan Iglesias <[email protected]> >> wrote: >> > >> > Hello Martynas >> > >> > I think it's not exactly what I had in mind. On your site I could see a >> > group of Semantic web sites accessible from your portal, and this portal >> > generates a basic user interface, automatically I suppose. I suppose it's >> > very easy to add new sites or repositories, and your platform generates a >> > basic view-controller for the site, or allows the user to define their own >> > view-controller. Correct me if I'm wrong, please. >> > >> > My idea is that my framework allows the addition of other plug-ins to >> > manage a single site, the complexities of a single site or repository and >> > help the programmer or admin to manage the Jena capabilities and >> > associated plug-ins graphically. Of course it could be linked with other >> > sites or repositories. >> > >> > I thought in having a very dynamic and ajax based VIEW, for example using >> > the ZK framework. >> > >> > Because around java there a lot of framework and utilities [the most I >> > think], the core technology has to be Java based. >> > >> > Thank you for your answer. >> > >> > Best regards >> > >> > Joan >> > >> > >> > >> >> Date: Mon, 25 Jun 2012 20:26:18 +0200 >> >> Subject: Re: Planning for a new framework for Jena >> >> From: [email protected] >> >> To: [email protected] >> >> >> >> Joan, >> >> >> >> could Graphity approach be similar to what you have in mind? >> >> http://www.w3.org/2011/09/LinkedData/ledp2011_submission_1.pdf >> >> >> >> You can see what kind of UI it can render on http://linkeddata.dk. >> >> >> >> Martynas >> >> graphity.org >> >> >> >> On Mon, Jun 25, 2012 at 7:57 PM, Joan Iglesias <[email protected]> >> >> wrote: >> >> > >> >> > Hello Rob >> >> > >> >> > Commends inline also. >> >> > >> >> >> From: [email protected] >> >> >> To: [email protected] >> >> >> Subject: Re: Planning for a new framework for Jena >> >> >> Date: Mon, 25 Jun 2012 17:01:30 +0000 >> >> >> >> >> >> Hi Joan >> >> >> >> >> >> Comments inline: >> >> >> >> >> >> >> >> >> On 6/25/12 9:30 AM, "Joan Iglesias" <[email protected]> wrote: >> >> >> >> >> >> > >> >> >> >Dear all >> >> >> > >> >> >> >I'm new at this list, but I would like to purpose the building of a >> >> >> >new >> >> >> >framework for Jena. >> >> >> > >> >> >> >I'll be in charge of the design and programming of this new framework, >> >> >> >but new ideas or collaborations with other developers are welcome. >> >> >> > >> >> >> >The project is a java web platform for configuring, managing and >> >> >> >queering >> >> >> >the Jena framework from any web browser. That framework will allow the >> >> >> >users to save time in the configuration time, initial contact and >> >> >> >database administration of Jena framework. It could be .war for any >> >> >> >application server with the appropriate configuration files. >> >> >> >> >> >> Please take a look at JENA-201 >> >> >> (https://issues.apache.org/jira/browse/JENA-201) which contains a >> >> >> discussion on how to convert the existing Fuseki architecture into WAR >> >> >> form. If you are interested maybe you would like to work on >> >> >> contributing >> >> >> towards that effort? >> >> >> >> >> >> Also Fuseki already includes much of the configuration, management and >> >> >> querying capabilities you are talking about. Granted right now Fuseki >> >> >> can't easily be run in any Java application server because it runs off >> >> >> an >> >> >> embedded Jetty but if that issue was addressed this would become >> >> >> possible. >> >> >> And equally the built in UI could be a little less basic but none of >> >> >> us >> >> >> Jena developers claim to be graphic design or UX experts! >> >> > >> >> > I'm not an expert on Jena, I only read some tutorials about Jena and >> >> > its frameworks. Of course the development of such a framework needs >> >> > much more knowledge than I have. Because of this I suggested the >> >> > project to the Jena community, because I don't want to start a long >> >> > learning period if the framework is useless or not needed for the >> >> > community or already exists something similar. >> >> > >> >> > Like all technologies, the more user-friendly user interface, the most >> >> > success in the adoption of the technology. Some companies if they >> >> > appreciate a long learning period of a framework, the framework is >> >> > discarded. >> >> > >> >> > I could deduce from the tutorials of fuseki an so on, that most of the >> >> > configuration is done by file configuration. The idea of my project, >> >> > it's that you just download the war file, you deploy it, and all the >> >> > configuration and management is done using a very helpful and >> >> > user-friendly interface. Addition of modules, database configuration >> >> > and administration, and so on. >> >> > >> >> > I think, that any developer prefer a tool, self explanatory with small >> >> > time to learn how it works. >> >> > >> >> > Maybe such a framework could be developed using fuseki code or other >> >> > Jena frameworks as a base framework or starting framework. >> >> > >> >> > The platform I propose, it allows to manage plug-ins graphically, like >> >> > Eclipse, for example. And a plug-in could have it's own web interface >> >> > to configure or use it. I think that those functionality it's not >> >> > possible by now using fuseki. >> >> > >> >> > For example, is there any framework that allows to manage ontologies >> >> > graphically and integrated into Jena? Sometimes I think it's very >> >> > useful that a plug-in has a web interface, like the case I mentioned >> >> > before, and integrated into a well defined platform. >> >> > >> >> > What do you think about all this?? >> >> > >> >> >> >> >> >> > >> >> >> >I consider that it has to be designed in a modular way, and the >> >> >> >addition >> >> >> >of new plug-ins have to be taken into acount from the very begginng. I >> >> >> >thought it could be like a kind of Eclipse, that it's a platform for >> >> >> >development with basic functionalities, but allows the additions of a >> >> >> >lot >> >> >> >of plug-gins from the community or private companies. >> >> >> >> >> >> This is basically what the Jena platform is already unless I am >> >> >> misunderstanding your point? >> >> >> >> >> >> I don't know how familiar you are with Jena (I assume at least >> >> >> reasonably >> >> >> so given the scope of your proposal) but Jena already has many >> >> >> extension >> >> >> points that can be utilized and many people using Jena commercially >> >> >> already use these widely. Maybe you could elaborate on exactly what >> >> >> it is >> >> >> that you want to extend/do that you don't think Jena can do right now? >> >> >> You may find that the types of extensions you want are already >> >> >> possible in >> >> >> the existing framework and you are just not aware of it. >> >> >> >> >> >> For example within Fuseki you can already leverage the Jena assembly >> >> >> mechanism for loading and executing arbitrary code allowing you to add >> >> >> custom functionality to a standard Fuseki distro to some extent. >> >> >> >> >> >> > >> >> >> >Some of the nowadays utilities for Jena could be migrated into a >> >> >> >plug-in >> >> >> >for this platform. REST and SOAP services could be a plug-in for this >> >> >> >platform. >> >> >> >> >> >> Utilities such as? >> >> >> >> >> >> > >> >> >> >New ideas or suggestions are welcome. I think a framework like this >> >> >> >will >> >> >> >help Jena to be more used, because the intention is that the new >> >> >> >framework has to be in most of the cases "self explanatory" and >> >> >> >intuitive, and with a lot of helping tools. >> >> >> >> >> >> While I do want to discourage you from contributing to the Jena >> >> >> ecosystem >> >> >> it would be interesting to here some more detail on what exactly you >> >> >> want >> >> >> to build. From reading your email I get the impression that maybe a >> >> >> lot >> >> >> of what you want may already be available and you're just looking to >> >> >> get >> >> >> it more solidly integrated into a user friendly web based UI? >> >> >> >> >> >> Regards, >> >> >> >> >> >> Rob Vesse >> >> >> >> >> >> > >> >> >> >Best regards, >> >> >> > >> >> >> >Joan >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> > >> > >
