2 ms·
>> Also I wonder how helpful Prolog infrastructure could be since they provided some useful frameworks [3][4] for that. That's a good point, because looking at
by YeGoblynQueenne 6y ago
>> Also I wonder how helpful Prolog infrastructure could be since they provided some useful frameworks [3][4] for that.
That's a good point, because looking at the working paper on the proposed architecture of the project [1], the example of a "constructor" in Figure 1 is basically a set of frames and it has a straightforward translation in Prolog and the example of a "renderer" in English is basically a pattern with holes that also has a very straightforward Prolog implementation via Definite Clause Grammars. In fact the whole architecture reminds me a lot of IBM's Watson - the good bits (i.e. the Prolog stuff they used to store the knowledgebase).
________
[1] https://arxiv.org/pdf/2004.04733.pdf https://arxiv.org/pdf/2004.04733.pdf
- JadeNB 6y agoReminder to link to abstracts, rather than directly to PDF: https://arxiv.org/abs/2004.04733 https://arxiv.org/abs/2004.04733 .
- YeGoblynQueenne 6y agoOh, sorry. My bad and thanks for posting the link to the abstract.
- Ninjaneered 6y agoCan you explain why this is preferred? Is it to ensure everyone knows where it comes from (journal or preprint)?
- JadeNB 6y agoFor me, at least two reasons: 1. As you say, to see more information about where the paper comes from. 2. It's easy to get from the abstract page to the PDF, but not vice versa. Personally, I also think it's good for people to get into the habit of linking to a text description of data-heavy resources rather than directly to the resources. PDFs aren't that data-heavy, but there are plenty of other things that are that could do with a text landing page, and I think it's good to get in that habit.
- Ninjaneered 6y agoMakes sense, thanks!