I have been thinking about this a bit more and am of the opinion that any new documentation should be "within" the current website and therefore the WIKI may not be the best solution.
Perhaps the easiest start would be to create a section titled "Usage and Design Patterns" in the site under the documentation section. I would propose that we place in this section items that are either longer than the "howto" currently found in the "notes" section or that span multiple components. Documents in this section would be accepted in two basic formats: 1) web (mdtext/html), may be multiple pages. 2) downloadable (pdf?), must include a single web page describing the document and providing the link to the download which would be in the jena documentation directory. Information required within the document should be: author, original date, version of Jena and associated libraries, date of last update. Is there any objection or additions to the above? Claude On Tue, Jul 30, 2013 at 1:44 PM, Andy Seaborne <[email protected]> wrote: > On 24/07/13 09:06, Sarven Capadisli wrote: > >> On 07/24/2013 09:51 AM, Claude Warren wrote: >> >>> I was just responding to a question on the users list concerning >>> federated >>> queries and thought that it might be handy to have a set of documents >>> that >>> describe how people are using Jena and how they overcome specific issues. >>> Not sure if there would be much in the way of contribution but I would >>> post overviews of how we solved various problems in the projects I have >>> been involved in. Is there any interest from other developers? >>> >> > Yes. > > > >>> If so, I was thinking perhaps a wiki would be in order, if we can lock >>> down the authorship to keep spam out. >>> >> > The project has > > https://cwiki.apache.org/**confluence/display/JENA/<https://cwiki.apache.org/confluence/display/JENA/> > > and there is also > > http://wiki.apache.org/**general/ <http://wiki.apache.org/general/> > > Andy > > > >>> Thoughts? >>> >>> Claude >>> >>> >> I think this would be useful for the community, even a FAQ type of stuff >> would be handy. Or open problems that we don't yet know how to deal with. >> >> Keep in mind that >> http://answers.semanticweb.**com/<http://answers.semanticweb.com/>contains >> useful Q&As >> which we could make it to the Jena wiki - a cleaned up, perhaps a step >> by step on how-tos for some questions. >> >> Ditto the users mailing list. >> > > Yes - the best first step is generate some content at minimal overhead. > If it proves successful, it can be organised. > > Claude - thoughts? > > >> -Sarven >> >> > -- I like: Like Like - The likeliest place on the web<http://like-like.xenei.com> Identity: https://www.identify.nu/[email protected] LinkedIn: http://www.linkedin.com/in/claudewarren
