W3C home > Mailing lists > Public > public-xg-lld@w3.org > April 2011

Re: VS: Transclusing the final report

From: Antoine Isaac <aisaac@few.vu.nl>
Date: Wed, 13 Apr 2011 20:29:14 +0200
Message-ID: <4DA5EB7A.6000500@few.vu.nl>
To: "public-xg-lld@w3.org" <public-xg-lld@w3.org>
Hi Kim,

I'm not sure I understand it, but I guess it will be clearer once I see it in action :-)

Antoine


> Hello Antoine,
>
> Ok, good. This means that I didn't miss some huge amounts of document parts that also should go to the final report. :)
>
> Javascript (or some other script): yes, the transclusions is automatic, but updating the "DraftReportWithTransclusions" page is not. That the input for the script would be the DraftReport wikipage (which contains both text and links, where from some links should be replaced to be the transclusion commands) and then outputted this to the DraftReportWithTransclusion wiki page. Just to avoid errors when copy-pasteing the body text of the DraftReport page. (I'll do the first version now by hand, but later on might write the script if needed.)
>
> Regards,
> Kim
> ________________________________________
> Lähettäjä: Antoine Isaac [aisaac@few.vu.nl]
> Lähetetty: 13. huhtikuuta 2011 15:21
> Vastaanottaja: Viljanen Kim
> Kopio: public-xg-lld@w3.org
> Aihe: Re: Transclusing the final report
>
> Hi Kim,
>
> I had warned you, we have not much to put in the report right now :-)
> As a matter of fact the draft many sections are not yet started.
> I think currently we only have draft pages for:
> - the benefits section (which will be "prosed" soon): http://www.w3.org/2005/Incubator/lld/wiki/Draft_Benefits
> - the problems and limitation section: http://www.w3.org/2005/Incubator/lld/wiki/Draft_issues_page
>
> And I'm not even sure that these are transclude-able into some report.
>
> The other material of the previous transcluded draft (http://www.w3.org/2005/Incubator/lld/wiki/Draft_issues_page) would now be moved to separate deliverable. Especially for the use cases (btw, @everyone, I'm not sure what the use case section of the report should contain now: a summary from the separate deliverable?)
>
> Also, I'm a bit puzzled when you mention a Java script: isn't the transclusion automatically kept up-to-date by virtue of the current mechanism? Or is the idea to make your own transclusion to solve some of the issues, like the re-use as such of the heading levels from the included page to the including page, which causes structure issues?
>
> Cheers,
>
> Antoine
>
>
>> To: Antoine or anybody,
>>
>> Hello!
>>
>> I promised in the previous telecon on 7th of April to do the transclusion of the final report. (Transclusions = including the content from some other wiki page to the current page, to make a long document that contains everything. Makes it e.g. easier to print the whole final report.)
>>
>> However, when I now looked at the final report [1], it was not clear to me what should/could be transcluded and what should not. (I was thinking about writing a small javascript or so to do the transclusion automatically.)
>>
>> My questions:
>>
>> 1) The H3 level topics with links (e.g. Bibliographic data, Authority data, ...) seem like likely candidates for transclusion. Any other parts in the document you think should be transcluded?
>>
>> 2) There are mentions in the page "Topics to be included here (with transclusion):" refering to "Category:CM.FRS" and "Category:LLD.VOCABS-STATUS", however there are no pages in any of these categories...
>>
>> If possible, I will write a simple Java?Script to do update transclusion page [2] automatically. To make things easier. :)
>>
>> Regards,
>> Kim
>>
>> [1] http://www.w3.org/2005/Incubator/lld/wiki/DraftReport
>> [2] http://www.w3.org/2005/Incubator/lld/wiki/DraftReportWithTransclusion
>>
>> --
>> Kim Viljanen, Semantic Computing Research Group, Aalto University, Finland
>
Received on Wednesday, 13 April 2011 18:27:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 13 April 2011 18:27:47 GMT