[Attempto] Workflow management and no-code apps creation

[Vijay Saraswat]

Are Attempto folks looking to modernize, keeping in mind Bert abd friends, incl GPT3 ?

Sent from my iPhone

> On Dec 23, 2020, at 8:41 AM, Norbert E. Fuchs <fuchs at ifi.uzh.ch> wrote:
> 
> 
> 
>> On 22 Dec 2020, at 11:39 , Igor Kryltsov <kryltsov at gmail.com> wrote:
>> 
>> Hello,
>> 
>> I am trying to create a system that will allow users to create applications to manage repeatable workflows (customer setup, employee onboarding, supplier order, end of year accounting report, promo campaign).
>> 
>> For now, I will stick with NL wizards where a user will be guided through a series of questions with predefined answers. Ideally, I want to allow users to use blueprints in ACE to describe their applications, load them into the system, get it immediately tested, correct ACE, and repeat until the desired result is received. No-code apps creation without a conventional approach of starting with spreadsheets concept used by AppSheets, Honeycode, or AirTable.
>> 
>> This is not ACE yet but an attempt to speak in it (sort of) https://docs.google.com/document/d/1NYr59C939MWet6YgSHl5Gfc19-CxWXoIBFikYCUChGM/edit?usp=sharing
>> 
>> Since my system is only about workflow management, users will not need to describe such a concept as dependencies and it will use a much smaller dialect that will probably be guided to be created with plenty of use cases already written in ACE to load and try.
>> 
>> I have a few questions
>> 
>> - do you see anything in my writing that will not be possible to express in ACE
>> 
>> - can ACE and APE be used in commercial projects under GNU? I see the license here (https://github.com/Attempto/APE/commit/72c6ab255949c5cbb0e3b8b9d37acff993376bcb). Does it apply to ACE too?
>> 
>> - When I say 'A lesson is a recurring workflow' I basically want to build an application called 'Lessons' and need to refer to 'lesson' as a single unit. An application called 'Lessons' will have multiple instances of 'lesson'. Since these are common English words how do I do about properly defining them?
>> 
>> I see http://attempto.ifi.uzh.ch/site/docs/ace_constructionrules.html (Proper Names) but no example of how to make definitions of not proper concepts so to speak.
>> 
>> Will using http://attempto.ifi.uzh.ch/race/ be the best way to iterate and learn ACE?
>> 
>> Right now I have:
>> 
>> Lessons is an application. A lesson contains a name, a planned start date, a Google Drive folder, and a n:workflow.
>> 
>> and it returns 2 errors. Here is another attempt:
>> 
>> Lessons_1 is an application.  A lesson is part of Lessons_1. Lessons_1 can contains lessons. A lesson has a property called 'Name'. A lesson has a property 'Planned start date'. A lesson has a property Google Drive folder. A lesson has a property n:workflow. 'Planned start date' is a date. Google drive folder is URL.
>> 
>> If you can recommend any paper that contains a more relevant dictionary for my use case I would truly appreciate it.
>> 
>> Please feel free to leave comments on my Google Doc
>> 
>> Thank you 
>> Igor
>> https://www.linkedin.com/in/igorkryltsov/
> 
> 
> Igor
> 
> Here are my answers to some of your questions.
> 
>> This is not ACE yet but an attempt to speak in it (sort of) https://docs.google.com/document/d/1NYr59C939MWet6YgSHl5Gfc19-CxWXoIBFikYCUChGM/edit?usp=sharing
>> ...
>> - do you see anything in my writing that will not be possible to express in ACE
> 
> The most efficient way to answer this question is to submit your text to APE. I did and APE generated a lot of error messages predominantly related to unknown words. So you have either prefix them as the error messages suggest or create your own lexicon or extend the lexicon that comes with APE. Furthermore, scanning your text I noticed that you occasionally omit the determiners that proper nouns require.
> 
>> - can ACE and APE be used in commercial projects under GNU? I see the license here (https://github.com/Attempto/APE/commit/72c6ab255949c5cbb0e3b8b9d37acff993376bcb). Does it apply to ACE too?
> 
> ACE is free to use and you could reimplement a parser for it, as in fact some people did for an earlier version. However, APE – as Pierre-Alexandre Voye already pointed out – comes with an LGPL licence. Please read all about the GNU Lesser General Public License at http://www.gnu.org/licenses/lgpl-3.0.html.
> 
>> - When I say 'A lesson is a recurring workflow' I basically want to build an application called 'Lessons' and need to refer to 'lesson' as a single unit. An application called 'Lessons' will have multiple instances of 'lesson'. Since these are common English words how do I do about properly defining them?
> 
> The indefinite noun "a lesson" is understood as an existentially quantified item. If I understand correctly what you want to achieve, it seems better to use universal quantification, i.e. "every lesson".
> 
>> I see http://attempto.ifi.uzh.ch/site/docs/ace_constructionrules.html (Proper Names) but no example of how to make definitions of not proper concepts so to speak.
> 
> This I do not understand. What are "not proper concepts"?
> 
>> Will using http://attempto.ifi.uzh.ch/race/ be the best way to iterate and learn ACE?
> 
> No, RACE is a reasoner for ACE. ACE is defined by its construction rules and interpretation rules that are implemented in APE. So read the construction rules and interpretation rules for the background, and use (the web-interface of) APE to get practical experience with ACE.
> 
>> Right now I have:
>> 
>> Lessons is an application. A lesson contains a name, a planned start date, a Google Drive folder, and a n:workflow.
>> 
>> and it returns 2 errors.
> 
> Read the error messages that hint to what is not correct. Concretely: The common noun "Lessons" lacks a determiner and is thus interpreted as a proper noun, that however is not in the lexicon. I guess, you want to say "very lesson is ...". Items of an enumeration like in "A lesson contains a name, a planned start date, a Google Drive folder, and a n:workflow." must be conjoined by "and". You cannot use commas here.
> 
>> If you can recommend any paper that contains a more relevant dictionary for my use case I would truly appreciate it.
> 
> No, you must create your own lexicon or extend the one that comes with APE.
> 
> Maybe, instead of experimenting you should spend some time to read the construction rules and interpretation rules.
> 
> Best regards.
> 
> Norbert E. Fuchs
> Department of Computational Linguistics
> University of Zurich
> 
> 
> 
> 
> 
> _______________________________________________
> attempto mailing list
> attempto at lists.ifi.uzh.ch
> https://lists.ifi.uzh.ch/listinfo/attempto