[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [docbook-elearning] DocBook <topic> element proposal
hi Scott, Yes I see what you're saying, but the a docbook resource could be just a chapter too, not necessarily an entire book. Oh, right--now I get it, a 'section' can be standalone but cannot be a valid docbook document by itself. sorry for the noise, I see the point now. --Tim > -----Original Message----- > From: Scott Hudson [mailto:scott.hudson@flatironssolutions.com] > Sent: Tuesday, February 09, 2010 4:46 PM > To: docbook-elearning@lists.oasis-open.org > Cc: Justus.Piater@ULg.ac.be > Subject: Re: [docbook-elearning] DocBook <topic> element proposal > > Hi Tim, > > you could certainly declare a docbook document as a resource. The topic > proposal is to allow a much more granular object that contains only the > content for that topic. If you use a full book as a resource, for > example, there is likely to be too much content for the particular > module you want to use this in. > > As Bob explained, section is a typical granular level of content, but > expects to be a part of some larger container (such as chapter, preface, > appendix, etc.). The topic would be a standalone unit of content. > > In the case of eLearning, the topic could easily be a reusable learning > object (resource), useful in more than one module. > > There are some other ways that assemblies can "cast" resources so they > are rendered at a particular level, but that may be too complex to get > into right now. > > HTH, > > --Scott > > On 09-Feb-10 2:07 PM, Tim Arnold wrote: > > hi Scott, > > I like the topic element, but from our talk this morning couldn't we get > the same capability by specifiying a docbook document (with sections for > clarity) as a "resource"? > > > > I see that the rules for topic would be much more restrictive, but I’m not > sure why it's so important to differentiate a topic from a section except > that topics must be standalone. Of course a docbook document as a resource > would be standalone. > > > > On the other hand, using a resource in that method may be an abuse of the > element. > > What do you think? > > > > --Tim > > > > > > > >> -----Original Message----- > >> From: Scott Hudson [mailto:scott.hudson@flatironssolutions.com] > >> Sent: Tuesday, February 09, 2010 4:00 PM > >> To: docbook-elearning@lists.oasis-open.org > >> Cc: Justus.Piater@ULg.ac.be > >> Subject: [docbook-elearning] DocBook<topic> element proposal > >> > >> FYI, here is a link to the proposed<topic> element from Bob Stayton: > >> http://www.mail-archive.com/docbook@lists.oasis-open.org/msg05227.html > >> > >> Please review and provide feedback (to this list, or on the general > >> docbook-apps list). I'd like for our SC to determine if this would be a > >> useful structure for eLearning content and whether further enhancements > >> will be needed. > >> > >> Thanks and best regards, > >> > >> -- Scott > >> > >> Scott Hudson > >> chair, DocBook subcommittee for eLearning > >> > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe from this mail list, you must leave the OASIS TC that > >> generates this mail. Follow this link to all your TCs in OASIS at: > >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]