hello, On Tue, Jul 28, 2009 at 2:03 PM, Guillaume Lerouge <[email protected]>wrote:
> Hi Ricardo, > > On Tue, Jul 28, 2009 at 1:47 PM, [Ricardo Rodriguez] Your EPEC Network ICT > Team <[email protected]> wrote: > > > > > > > Pascal Voitot wrote > > > I'm not the guy to give you any answer but I'm interested in this > idea... > > > What do you mean exactly by "guide the edition complying with this > > schema"? > > > Should it be just metadata associated with the doc or should the doc > > follow > > > a template based on this schema or is it a kind a form associated to > the > > > document? > > > > > > > > > > Great to hear than anybody else thinks that this could be a "no so > > stupid idea" It is a pity that the idea is not mine :-) > > > > Any document must follow the rules or grammar set in the schema. A > > really simple example. Thing about an scientific paper, or a business > > report, or a medical history. We could define a common set of features > > to each "family" of documents. For instance, it is commonly accepted > > that a scientific paper must content at least a summary, an > > introduction, material and methods, results discussion and bibliography. > > Introduction usually content a number of paragraphs, but no tables, no > > images, no lists. Results could content tables and/or pictures. > > Bibliography, a list of references. This structure could be described by > > an schema, whatever language is used for that. > > > > What I am looking for is to know how long, or close, is XWiki to be able > > to guide de edition of a new document belonging to one of this > "families". > > > > DocBook is a much more complex schema suited to write books and papers > > about computer hardware and software. > > > > Of course there is a whole universe out there dealing with this topics. > > > > The question here is of XWiki is, or has the possibility of being, able > > to be one of this "no so stupid" ideas that will ease the path to > > start-ups not needing the whole complexity of SGML/XML driven, or > > guided, editing. > > > > Looking at the new rendering module (general architecture)... > > > > http://code.xwiki.org/xwiki/bin/view/Modules/RenderingModule > > > > ... there are a number of supported syntaxes listed there. Parsers for > > each syntax will, optionally, generate a XDOM object suitable for > > transformations and that will be the entry for the renderers. My guess > > is that it will be possible to use a given parser at entry time. It > > probably won't be be called a parser in this case! The point is to have > > a tool that, in a given document, only allow entries complying with the > > rules/grammar defined in a given schema (again, whatever language is > > used to write it). > > > > > > > > I would not like to mess up things here. I am far from having a clear > > idea about the field I am talking about. But at the same time, I do need > > to talk with somebody/read more and more to clear up things! So, please, > > excuse me if these posts are not plenty or erudition. And, please, don't > > hesitate to tell me if this not the right place to post about this. > > > > Thanks for your time, > > > Not sure that's what you're looking for (since you're talking language + > grammar), but there might be a simple way to create this in XWiki using > XClasses & XObjects. Basically you would have to define a set of classes > and > then write some code to make them display together nicely: > > - One ScientificPaperClass with the following string properties: > summary, introduction, > materialAndMethods, resultsDiscussion, bibliography + metadata associated > to > the paper: authors, date, topic, etc... > - ScientificPaperClassSheet where you can edit those metadata fields + > select the relevant pages for each section > - A SummaryClass + an IntroductionClass + a ParagraphClass > - On the SummaryClassSheet and the IntroductionClassSheet, you add a > button allowing the user to add only ParagraphClass XObjects to > an instance > of the SummaryClass or IntroductionClass page > - A MaterialsAndMethodsClass and a ResultsDiscussionClass + ImageClass, > TableClass, ReferenceClass each of which holds the metadata related to > the > item (author, date, source etc) > - On pages using one of those 2 classes, make buttons available (add > Text, add an Image, add a Table, add a Reference) to add various types > of > content to them > - You generate the bibliography automatically from ReferenceClass > XObjects available in the ScientificPaperClass composite document > > This short specification isn't perfect, but you get the geist of it. > > This means that the whole authoring tool would much more structured than > only using a specific language + grammar, but it would allow for a guided > edition process that would remain simple enough. We've actually been > working > on a similar project for one of our customers and it seems to be working > fine for them. > > Would that way of doing things suit your use case? > This is an implementation solution (one I've already used and that works pretty cool) The idea of the schema would certainly be also to manage this construction in an automatic manner... That's certainly the question behind this... Ricardo, am I right? > > Guillaume > > Ricardo > > > > -- > > Ricardo RodrÃguez > > Your EPEC Network ICT Team > > > > _______________________________________________ > > devs mailing list > > [email protected] > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > > -- > Guillaume Lerouge > Product Manager - XWiki > Skype: wikibc > Twitter: glerouge > http://guillaumelerouge.com/ > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
