[SMW-devel] Offline Semantic Forms

2013-11-22 Thread Benedikt Kämpgen
Hello Yaron, Hello Semantic forms experts, In our medical project I talked about at SMWCon [1], we have the following requirement: * We create a full-fledged form for annotating patients in an online SMW. * Physicians want to reuse that form to offline fill in the form for patients. Offline,

Re: [SMW-devel] Offline Semantic Forms

2013-11-22 Thread Krabina Bernhard
Hi Benedikt, I think your use case is VERY interesting. Are you aware of the Push extension [1]? I havent't used it yet, but it sounds promising. But having some kind of other possibility to solve your usecase would be quite intersting. -Bernhard [1]

Re: [SMW-devel] Offline Semantic Forms

2013-11-22 Thread Yury Katkov
Nice case! I remember the proposal to integrate Extension:Drafts with Semantic Forms but this sounds even more radical! I can tell from my journeys through SF code that this would be a challenge: the majority of form is generated on a server side. Benedikt, what do you think about using Miga for

Re: [SMW-devel] Offline Semantic Forms

2013-11-22 Thread Neill Mitchell
Hi Benedikt. What would the Physicians use to key in the data into the form? A laptop or PC/Mac based laptop? If this is the case there is nothing stopping them running a local copy of MW/SMW and then simply uploading the data to the central instance (a server somewhere I assume) using the

Re: [SMW-devel] Ask 1.0 released!

2013-11-22 Thread Jeroen De Dauw
Hey, Hopefully writing result formats will become even easier and more pleasant task! Hopefully it will yes! Though this will not be brought with using the Ask library, as the technical issues faced there are mostly disjoint from the Ask language. That being said, having a nicer implementation

Re: [SMW-devel] SRF JitGraph

2013-11-22 Thread Jeroen De Dauw
Hey Richard, This sounds interesting! The next release of SRF is scheduled for next month, so if this is still to get in before then, we need to be somewhat quick. (And not wait 8 days before replying to an email!) The typical workflow is to submit a patch, as a commit in our code review system