Re: [docbook-tc] DocBook Technical Committee Meeting Agenda: 14 Aug 2019

[Bob Stayton <bobs@sagehill.net>]

Hi,

Regarding action item g) issue #117 adding info to listitem, here is the changes proposed by Jirka.

Hi Bob,

I suppose info that doesn't allow title should be used there.

So changing

 db.listitem = element listitem {
ÂÂÂÂÂ db.listitem.attlist,
ÂÂÂÂÂ db.all.blocks+
ÂÂ }

to

 db.listitem = element listitem {
ÂÂÂÂÂ db.listitem.attlist,
ÂÂÂÂÂ db.titleforbidden.info?,
ÂÂÂÂÂ db.all.blocks+
ÂÂ }

should do the trick.

db.titleforbidden.info pattern defines info element that can't contain
title.

Bob Stayton
Sagehill Enterprises
bobs@sagehill.net

On 8/12/2019 2:17 PM, Scott Hudson wrote:

DocBook Technical Committee MeetingÂAgenda: 14 Aug 2019

=============================================================

The DocBook Technical Committee willÂmetÂon Wednesday,Â14 Aug 2019

(11am PDT, 12noon MDT, 1pm CDT, 2pm EDT, and 8pm CET)

Â

1.ÂÂRoll call

2. Accept the minutes [1] of the previous meeting (12 June 2019)

3. Next meeting:Â11 September 2019

4. Review of the agenda.Â

5. Review of open action items

a. Â Extension for synopsis elements

ÂÂÂÂÂÂÂÂÂÂÂ (Issue #111)

ACTION: All to review info element proposals and provide any feedback to Bob. Bob submitted samples to list 11FEB2019.CONTINUED.ÂResponse from Stefan, but we are looking for generic constructions that apply to multiple languages, not specifically C++. Would need a point by point comparison to adequately determine if the Summer of Code proposal would work.

Â

b. ACTION: Bob to contactÂdourouc05Â(from issues list) valuate the Summer of Code work to determine if the proposal works or if there are other gaps to be considered.

ÂÂÂ

c.ÂLarry to create an integrated proposal for legalsection, all to review before next meeting for approval.ÂÂÂCONTINUED.Â

ACTION: Bob to follow up with Norm and Jirka to get input. Plan to vote at next meeting.ÂNeed formal proposal to vote at next meeting.

d. ACTION: Bob to have Norm/Jirka document the integration process.

e. ALL: start work on action items earlier. CONTINUED

Some progress!Â

f. Scott to send a reminder mid-month.ÂCONTINUED

[still needs work!]

g.ÂÂÂÂÂÂ ACTION: (Issue #117 - allow info in listitem) Bob to follow up with Jirka to create a mocked-up schema change to vote on.ÂCONTINUED.

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂi.ÂÂÂÂÂÂThe info element is a bit complicated (some models with titles, some without). Jirka suggested to use the non-titled version.

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂii.ÂÂÂÂÂÂShould have a formal proposal to vote on at next meeting.Â

6. Social media presence for DocBook

Purpose: To raise awareness of actions (votes, calls for information, etc.)

ÂÂÂ

7. Review of Requests for Enhancement

To find a Github issue by number, enter the URL (on one line):

github.com/docbook/docbook/issues

Â

Open Issues (Note: items that have been accepted are still open

on Github until included in a release,

but they are not listed here):

Â

71 license tag

ÂÂ

78 Schema website should be updated

Â

93 Diff between doc of resource element and Assembly schema

ÂÂ

99 Add <endorsement> to <info>

Consider for Publishers.

Â

100 DocBook 5.1 catalog.xml uses incorrect version

Â

103 XML DTD of DocBook 5.1

ÂÂ

112Ârefentry in sect1

ÂÂÂÂÂÂÂÂÂÂ Â

111ÂDocBook Library (tentative name)Â- (Supercedes 107, 108, 109, 110; other issues closed by Scott 6/10).

Â

112 refentry in sect 1 - Needs to be addressed in schema. (bug fix)
ACTION: Bob to request schema change to Jirka/Norm to add the fix.

Â

117 Allow info in listitemÂ

associate some metadata with a listitem, but no place to put it.

Â

Links:

[1]Âhttps://lists.oasis-open.org/archives/docbook-tc/201906/msg00002.html

Â

[2]Âhttp://github.com/docbook/docbook/issues

Â

Thanks and best regards,

Â

--Scott

Â
Scott Hudson
Content Technology Strategist, DS&A Information and Knowledge Services

Jeppesen, A Boeing Company

55 Inverness Drive East

Englewood, CO 80112

303-328-6228Â| Cell: 303-350-7934

Â

Â

http://www.jeppesen.com