[00:03:47] This is what I'm hoping for. To call a wikifunction which returns Type:wikitext-fragment which is then parsed as usual. (re @amire80: So a function will be able to output Brooks, Frederick P. (1975). ''[https://archive.org/details/mythicalmanmonth00broo The Myth...) [00:05:07] If it works really well, you could then imagine calling such a function from a page in Template namespace, which would generate a template in your language for you... (re @Toby: This is what I'm hoping for. To call a wikifunction which returns Type:wikitext-fragment which is then parsed as usual.) [05:01:20] Based on our current plans: Yes, a function will be able to output links and italics. No, you won't be able to output wiki text that needs to be parsed again. (re @amire80: So a function will be able to output Brooks, Frederick P. (1975). ''[https://archive.org/details/mythicalmanmonth00broo The Myth...) [05:50:04] In the first iteration, or never any parsing on the client Wikis? (re @vrandecic: Based on our current plans: Yes, a function will be able to output links and italics. No, you won't be able to output wiki text ...) [05:52:34] The future is wide and open, but the current plan is not to enable parsing on the client wikis -- the architecure for that just doesn't work out. That would otherwise become really complicated. [05:57:13] So any Abstract Wikipedia content would be void of links and references, or am I missing some other crucial part? [05:58:35] Links should work. We understand the obvious necessity for Wikipedia-style references and are trying to figure that out, but do not yet have a solution for it. [06:04:58] If you have time, can you expand on "the architecture for that just doesn't work out"? What are the biggest obstacles? (re @vrandecic: The future is wide and open, but the current plan is not to enable parsing on the client wikis -- the architecure for that just ...) [06:05:56] Yes, I am working on a longer text for that. expanding on that. [06:11:43] But that will take a while, just to set expectations correctly [06:16:45] While you are at expectation setting, perhaps a mock up of what you think a great piece of Abstract Wikipedia content will look like on a client wiki when all planned features are in place? [06:24:45] That will be part of the text we are working on. [08:29:57] I have a vague sense of the technical challenges. But wikitext is just text, so the issue is with the subsequent parsing so, yeah, don’t do that. But unparsed wikitext would be what Abstract Wikipedia content would need to become for it to be integrated into the client-wiki content for subsequent refinement and extension. So do that, most definitely! (re @vrandecic: The [08:29:57] future [08:29:57] is wide and open, but the current plan is not to enable parsing on the client wikis -- the architecure for that just ...) [23:03:49] I may be misunderstanding, but you seem to be saying that the unparsed wikitext should be generated by WF then parsed at the point it reaches the client side wiki, not before. This seems to be the opposite of @vrandecic "not to enable parsing on the client wikis". (re @Al: I have a vague sense of the technical challenges. But wikitext is just text, so the issue is with [23:03:49] the subseq [23:03:49] uent parsing so, yea...)