Yeas, it's less twisted that way, though the meaning slightly differs. I would refine it further:
Usually, a general-purpose programming language (like Java) is used to prepare the data (issue database queries, do business calculations). Then, Apache FreeMarker displays that prepared data using templates. Tuesday, November 21, 2017, 9:48:24 PM, Denis Bredelet wrote: > Hi, > > I would like to change that sentence in the description: > You meant to prepare the data to display in a real > programming language, like issue database queries and do business > calculations, and then the template displays that already prepared data. > > What do you think of: > A general programming language is used to prepare the data, issue > database queries and do business calculations. Then the Apache > FreeMarker template engine displays that prepared data using templates. > > Cheers, > — Denis. > >> On 21 Nov 2017, at 19:47, Sergio Fernández <wik...@apache.org> wrote: >> >> On Tue, Nov 21, 2017 at 1:06 AM, Daniel Dekany <ddek...@apache.org> wrote: >> >>> Monday, November 20, 2017, 10:42:11 PM, Sergio Fernández wrote: >>> >>>> sorry, because I think I've created some confusion on this. Let me try to >>>> explain my self, because there are to aspects on this: >>>> >>>> 1) From a pure ASF perspective, host the DOAP file from Git is fine. The >>>> system behind projects.a.o will retrieve it and further process it. >>>> >>>> 2) From a broader Semantic Web perspective, ideally we should have the >>> DOAP >>>> file publicly available from the project web site. >>>> >>>> I aim for 2, that's why I played with the site build. But staying at 1 >>>> should be enough. I hope now it's a bit clearer. >>> >>> I see, but the URL we put into projects.xml is a HTTP URL, so why not >>> just add a link with that target address on the home page? That's one >>> less copy of that file that can go out if sync as well. (At that point >>> it doesn't even make sense anymore that it's inside "site", but >>> whatever...) >> >> >> it does for provenance reasons. But you can keep it at git, fine. > -- Thanks, Daniel Dekany
