Jirka Kosek | 2 Aug 2010 11:07
Picon
Favicon
Gravatar

Re: RE: Sections and topics

rob.cavicchio <at> emc.com wrote:

>> 3) XInclude always perform "Language Fixup" which is especially for
>>  non-English content real pain. You have to add explicit xml:lang
>> to each small piece of content you are going to XInclude.
> 
> I'm not sure what you mean by this, I haven't seen these types of
> inheritance problems with XIncludes, at least not with Arbortext
> Editor and our custom transform. But we're still on DocBook 4.5 and
> using the DocBook-specific "lang" attribute rather than "xml:lang",
> so maybe I just haven't run into it.

It is not problem for DocBook V4.X as it uses its own lang attribute
which is not specially processed by XInclude. But DocBook V5.0 uses
xml:lang. And if you XInclude fragment like

<para>FooBar</para>

inside some document

<article xml:lang="xx">
<title>...</title>
<xi:include href="foobar.xml" xmlns:xi="..."/>
</article>

you will effectively get:

<article xml:lang="xx">
<title>...</title>
<para xml:lang="">FooBar</para>
(Continue reading)

Alexander Garcia Castro | 3 Aug 2010 20:17
Picon

Natasha Noy and Peter Yim keynote speakers at SERES (ISWC), CfP -Semantic Repositories

--
Alexander Garcia
http://www.alexandergarcia.name/
http://www.usefilm.com/photographer/75943.html
http://www.linkedin.com/in/alexgarciac
Postal address:
Alexander Garcia, Tel.: +49 421 218 64211
Universität Bremen
Enrique-Schmidt-Str. 5
D-28359 Bremen

Jaime Lloret Mauri | 16 Aug 2010 17:52
Picon

Call for book chapters. Book title: Mobile Ad hoc Networks: Current Status and Future Trends


Call for book chapters

Book title: Mobile Ad hoc Networks: Current Status and Future Trends

Mobile Ad hoc Network (MANET) consists of a large number of mobile nodes with processing and wireless
transmission capability. MANETs are decentralized having dynamic topology. The major issues in MANETs
are the limited resources, mobility of the mobile nodes. Physical and MAC layer issues, routing in high
mobility, ensuring Quality of Service (QoS), security, all these are various facets of MANET research
issues. Though many of the issues have been solved from various points of views and for various types of
application scenarios, many other still remain as open research issues. This book will include advance
information of MANETs, current and existing mechanisms and development, and future expectations in
the relevant areas. The book could be a valuable reference book for researchers, industry professionals,
and academics. It could be used as a text book for graduate students as almost all the concerned areas will
be covered.

Guest Editors:

Shafiullah Khan, Kohat University of Science and Technology (KUST), Pakistan
Jaime Lloret, Polytechnic University of Valencia, Spain
Jesus Hamilton Ortiz, University of castilla y la Mancha, Spain
Jonathan Loo, School of Engineering and Information, Middlesex University, UK

Publisher:

CRC Press: Taylor and Francis
Auerbach-Publications,
www.auerbach-publications.com

Submission email: ijcnis <at> gmail.com

Deadlines:
Chapter Submission deadline: September 25th, 2010
Acceptance Notification: October 25th, 2010
Revised manuscript Submission: November 25th, 2010
Publication of book: second quarter of 2011. 
Bob Stayton | 17 Aug 2010 18:14

DocBook Technical Committee Meeting Agenda: 18 August 2010

DocBook Technical Committee Meeting Agenda: 18 August 2010
=============================================================

The DocBook Technical Committee will meet on Wednesday, 18 August 2010 at
01:00p EDT (10:00a PDT, 17:00GMT, 18:00BST, 19:00CEST, 02:00JST+,
022:30p India+) for 90 minutes.

Attendance at teleconferences is restricted to members
(and prospective members) of the committee.

This is the phone number for Wednesday's DocBook TC call:

Phone: +1-719-387-5556
 Code: 902213

The DocBook TC uses the #docbook IRC channel on
irc.freenode.org.  The IRC channel is used for exchanging
URIs, providing out-of-band comments, and other aspects
of the teleconference, so please join us there if at
all possible.

Agenda

1. Roll call
2. Accepting the minutes [1] of the previous meeting.
3. Next meeting: 15 September 2010
4. Review of the agenda.
5. Review of open action items

  a.  Norm to develop a proposal for maintaining the DocBook websites.

  b.  Larry to render the current reltable example from
      Bob and Norm with the current assembly elements for
      comparison.

  c.  Jirka to further develop proposal for transclusion in DocBook.

  d.  Norm to release DocBook 5.1b2 and announce it more widely.

  e.  Larry to create a sample of  <at> type in an assembly.

6.  Publishing Subcommittee report.

7.  eLearning Subcommittee report.

8.  Reltables in modular DocBook.

9.  Transclusion in DocBook.

Please see Jirka's updated proposal and discussion thread. [2]

10.  Release of DocBook 5.1 beta.

11.  Review of Requests for Enhancement

    To browse a specific RFE, enter the URL (on one line):

      http://sourceforge.net/tracker/index.php?func=detail&;
      group_id=21935&atid=384107&aid=XXXX

    RFEs to revisit for 6.0
      1907003  biblioid content model too broad  

    RFEs to be considered 
      1679665  Add better support for modular documentation  
      2820190  add a topic element  
      2820947  Ability to transclude text 
      2935829  Expand content model of sidebar 
      2964576  disallow table in entry  
      3035565  Allow sections at any level  

-----

[1] http://lists.oasis-open.org/archives/docbook-tc/201007/msg00031.html
[2] http://lists.oasis-open.org/archives/docbook-tc/201007/msg00041.html

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
Stefan Seefeld | 17 Aug 2010 19:45
Picon
Favicon

Re: DocBook Technical Committee Meeting Agenda: 18 August 2010

  On 08/17/2010 12:14 PM, Bob Stayton wrote:
> DocBook Technical Committee Meeting Agenda: 18 August 2010
> =============================================================

I'd like to suggest an addition to the agenda, if possible:

The potential addition of extension profiles (such as the API vocabulary 
that is being developed as a GSoC project this summer, or the Website 
and Slides extension profiles) suggests a policy to be defined for 
extension vocabularies, concerning (among others) the use of 
profile-specific namespaces.

The goal is to give users of such extension profiles the means to use 
the DocBook "core" vocabulary in conjunction with one or more extension 
vocabularies without the risk of element name collisions.

Thanks,
         Stefan

--

-- 

       ...ich hab' noch einen Koffer in Berlin...
Norman Walsh | 18 Aug 2010 19:50
Favicon
Gravatar

Announce: DocBook V5.1b2

Hello world,

I'd have sworn I sent this message last month, but there's no record
of it. I guess that mean's I'd be swearing in vain. In any event, last
month I released DocBook V5.1 beta 2, one of a series of experimental
releases that will take place as we evaluate V5.1.

For more information, see http://norman.walsh.name/2010/07/27/docbook51b2

For the schemas and documentation, see http://docbook.org/

Here's a quick summary:

The star feature of DocBook V5.1 is support for "topic-based"
documentation. At a minimum, that means we'll be adding a new
component-level element with the semantically neutral name “topic” and
providing some mechanism for composing topics.

Deciding to use <topic> makes a statement about the kind of
documentation that you're building. Although you can make a <book> of
topics, you can't mix topics willy-nilly amongst the more traditional
narrative elements.

Topics by themselves aren't especially useful, to reap the real
benefits of the topic-based authoring paradigm, you must be able to
reuse them, to compose them together into new modules or structures
(be they books, help systems, web sites, or what-have-you).

For this purpose, DocBook V5.1 introduces the <assembly>. Assemblies
are the mechanism by which authors can compose topics (or, in fact,
other narrative elements) together. My XML Prague presentation,
Automating Document Assembly in DocBook explored one toolchain for
processing assemblies. I've only just now realized that I never
published that anywhere else.

Tools support for topic-based authoring in DocBook is under active
development, as is the schema itself. I'll be presenting DocBook V5.1
at XML 2010 in Philadelphia this October.

Questions, comments, etc., most welcome on the DocBook mailing list.

Changes in DocBook V5.1b2

Here's a quick summary of the changes in DocBook V5.1b2 as compared to
the official DocBook V5.0 schema, in case you're interested in the
gory details.

    * Fixed RFE 1679665 Add better support for modular documentation
    * Fixed RFE 1722935 Add a proofreader value to the class attribute
      for <othercredit>
    * Fixed RFE 1770787 Add <givenname> as an alternative for <firstname>
    * Fixed RFE 1899655 Allow more elements to be the root of a DocBook document
    * Fixed RFE 2100736 Allow <constant> in <initializer>
    * Fixed RFE 2791288 Added several additional elements, including
      <quote>, to the ubiquitous inlines
    * Fixed RFE 2820190 Add a <topic> element
    * Fixed RFE 2821653 Remove the constraint that <indexterm>
      elements must not appear in <footnote>s
    * Fixed RFE 2907124 Allow personal name components directly in <bibliomset>.
    * Fixed RFE 2907125 Allow all inlines in <remark>
    * Fixed RFE 2907131 Allow <simplesect> in <colophon>
    * Fixed RFE 2964576 Fix the bug that allowed <table> to appear inside <entry>

                                        Be seeing you,
                                          norm

--

-- 
Norman Walsh <ndw <at> nwalsh.com>      | Time is a great teacher, but
http://www.oasis-open.org/docbook/ | unfortunately it kills all its
Chair, DocBook Technical Committee | pupils.-- Berlioz
Bob Stayton | 19 Aug 2010 00:26

DocBook Technical Committee Meeting Minutes: 18 August 2010

DocBook Technical Committee Meeting Minutes: 18 August 2010
=============================================================

The DocBook Technical Committee met on Wednesday, 18 August 2010 at
01:00p EDT (10:00a PDT, 17:00GMT, 18:00BST, 19:00CEST, 02:00JST+,
022:30p India+).

1. Roll call

Present:
Paul Grosso, Nancy Harrison, Scott Hudson, Gershon Joseph,
Jirka Kosek, Bob Stayton, Norm Walsh

Regrets: Dick Hamilton, Larry Rowland

2. Accepted the minutes [1] of the previous meeting.
3. Next meeting: 15 September 2010

This was changed to 22 September 2010.

4. Review of the agenda.

Add item 10b for API extension elements.

5. Review of open action items

  a.  Norm to develop a proposal for maintaining the DocBook websites.
      CONTINUED

  b.  Larry to render the current reltable example from
      Bob and Norm with the current assembly elements for
      comparison.
      CONTINUED

  c.  Jirka to further develop proposal for transclusion in DocBook.
      COMPLETED

  d.  Norm to release DocBook 5.1b2 and announce it more widely.
      COMPLETED

  e.  Larry to create a sample of  <at> type in an assembly.
      CONTINUED

6.  Publishing Subcommittee report.

The second review period of the publishers schema passed
with no new issues.  The Committee resolved and approved
it as a Committe Specification.  

ACTION: Scott to pursue official OASIS publication as a Committee Spec.

7.  eLearning Subcommittee report.

They did not meet this month.  Still working on assembling use
cases so requirements can be developed.

8.  Reltables in modular DocBook.

Continued.

9.  Transclusion in DocBook.

Please see Jirka's updated proposal and discussion thread. [2]

Jirka summarized the current proposal. Quite a bit of detail
was needed for the problem of duplicate ids when content is
included more than once. 

Gershon noted that the processing is complicated, but it is a
necessary complication to handle all the cases.

Norm asked about transformations from other vocabularies
during transclusion.  The Committee decided that was
out of scope, and should be done at the assembly level.

Next steps: Committee members will experiment with it for
a month. At the next meeting decide if we should include
it in the next DocBook 5 beta.

ACTION: Paul to consider implementation details.

ACTION: Jirka to email his open questions to the TC list.

10.  Release of DocBook 5.1 beta.

Norm completed the release of DocBook 5.1b2, but did not
announce it on the public docbook mailing lists.
He will correct that.

10b.  API extensions.

One project of the Google Summer of Code was developing
schema extensions for documenting programming APIs.
The developer asked the Committee about whether these should
be in the DocBook namespace, or a separate namespace?

The Committee felt that people are free to develop extensions
that make use of the DocBook namespace, because of the complications
in mixing namespaces.  However, the Committee wants to
distinguish between ad hoc extensions and those that are
reviewed and approved by the Committee as part of the
DocBook standard 11.

ACTION: Bob to write up a short policy statement about
the use of the DocBook namespace.

Review of Requests for Enhancement

    To browse a specific RFE, enter the URL (on one line):

      http://sourceforge.net/tracker/index.php?func=detail&;
      group_id=21935&atid=384107&aid=XXXX

    RFEs to revisit for 6.0
      1907003  biblioid content model too broad  

    RFEs to be considered 
      1679665  Add better support for modular documentation  
      2820190  add a topic element  
      2820947  Ability to transclude text 
      2935829  Expand content model of sidebar 
      2964576  disallow table in entry  
      3035565  Allow sections at any level  

The only new item was 3035565.  Bob pointed out that this was
motivated by a need for modular source files, but pointed out
that the assembly mechanism would be better.  

ACTION: Bob to respond to the RFE.

-----

[1] http://lists.oasis-open.org/archives/docbook-tc/201007/msg00031.html
[2] http://lists.oasis-open.org/archives/docbook-tc/201007/msg00041.html

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
Dave Pawson | 19 Aug 2010 11:01
Picon

Re: Announce: DocBook V5.1b2

On Wed, 18 Aug 2010 13:50:26 -0400
Norman Walsh <ndw <at> nwalsh.com> wrote:

> Hello world,
> 
> I'd have sworn I sent this message last month, but there's no record
> of it. I guess that mean's I'd be swearing in vain. In any event, last
> month I released DocBook V5.1 beta 2, one of a series of experimental
> releases that will take place as we evaluate V5.1.
> 
> For more information, see
> http://norman.walsh.name/2010/07/27/docbook51b2
> 
> For the schemas and documentation, see http://docbook.org/

Feature request please Norm.
docbookxi is missing the two comments //comment()[1] and 2
which provide the version information?
Ditto assembly, dbits

As provided in docbook.rnc

Nice to see it reduced to one file!

-- 

regards 

--

-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
Kasun Gajasinghe | 19 Aug 2010 12:17
Picon

A separate Index Tab for DocBook WebHelp?

Hello list,
what do you think about having $subject along with "content" and "search" in the content pane to the index rather than having a just a link in the content pane? 
I think it will make the navigation easier, isn't it?


Thanks,
--Kasun

~~~*******'''''''''''''*******~~~
Kasun Gajasinghe,
University of Moratuwa,
Sri Lanka.
Blog: http://kasunbg.blogspot.com
Twitter: http://twitter.com/kasunbg
Dave Pawson | 19 Aug 2010 14:11
Picon

Re: A separate Index Tab for DocBook WebHelp?

On Thu, 19 Aug 2010 15:47:08 +0530
Kasun Gajasinghe <kasun.gajasinghe <at> gmail.com> wrote:

> Hello list,
> what do you think about having $subject along with "content" and
> "search" in the content pane to the index rather than having a just a
> link in the content pane?
> I think it will make the navigation easier, isn't it?
> 
> Current output demo is at:
> http://www.thingbag.net/docbook/gsoc2010/doc/content/ch01.html
> 
> Thanks,
> --Kasun

I'm not very impressed with the accessibility Kasun?
Just try tabbing from the address bar?

-- 

regards 

--

-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

Gmane