OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-tc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-tc] Groups - Meeting Minutes 20 July 2016 uploaded

Hi Jirka,

You’re right, the July minutes did get corrupted. The TC agreed to add a danger element, but because I put that element in brackets in the minutes, it looks like the mailer tried to interpret it as an element and it got removed from the text. I’ll update the minutes to fix that.

Best regards,
XML Press
XML for Technical Communicators

> On Sep 18, 2016, at 15:14, Kosek, Jiri (LNG-HBE) <jiri.kosek@lexisnexis.co.uk> wrote:
> Hi folks,
> I'm trying to prepare schema with all recently approved changes. However these minutes seems little bit damaged and I don't see which element you decided as a new admonition. Was it originaly proposed *danger* or something else?
> Many thanks in advance,
> Jirka
> From: docbook-tc@lists.oasis-open.org <docbook-tc@lists.oasis-open.org> on behalf of Richard Hamilton <hamilton@xmlpress.net>
> Sent: 20 July 2016 21:21:41
> To: docbook-tc@lists.oasis-open.org
> Subject: [docbook-tc] Groups - Meeting Minutes 20 July 2016 uploaded
> Submitter's message
> DocBook Technical Committee Meeting Minutes: 20 July 2016
> =============================================================
> The DocBook Technical Committee met on Wednesday,
> 20 July 2016 at 2:00pm ET
> 1. Roll call
> Present: Bob Stayton, Scott Hudson, Larry Rowland,
> and Dick Hamilton. Quorum met.
> 2. Accepted the minutes [1] of the previous meeting.
> 3. Next meeting: 17 August 2016
> 4. Review of the agenda.
> Bob: add discussion about handling minutes.
> 5. Review of open action items
> a. Norm to review the non-normative XML Schema version of 5.1
> to make sure it has all the latest changes.
> b. Norm to complete his XInclude implementation.
> c. Bob to investigate assembly for XInclude equivalents.
> d. Larry will look into ISO standards for admonitions.
> COMPLETE: see discussion below
> New Item: How to handle minutes.
> We will start using the OASIS process, which archives the minutes
> and sends them to the TC mailing list. Dick will cc the DocBook mailing list.
> 6. Status of stagedir elements in Publisher's. See [2].
> Email from Radu Coravu reported that and 
> are not in the publisher's schema as distributed with Oxygen. This led
> to a discussion of where the schema should live in its current state.
> These elements depend on 5.1, so they are not in the OASIS repository.
> ACTION: Bob will discuss with Norm how Publisher's fits into the Github structure.
> ACTION: Scott will verify that the items accepted for 1.1 are represented in a schema,
> make that schema available, and respond to the email.
> 7. DocBook 5.1 release
> Bob spoke with Chet Ensign to see what needs to happen to make 5.1
> a Candidate OASIS Standard. The changes are all formatting and do not
> require changes to the standard. Norm set up a custom process to build
> the deliverables. Bob converted the files and process back to the method
> OASIS uses and is now using the OASIS standard tools. He created a version
> of the Candidate OASIS Standard using those tools and sent it to Chet on
> Monday. Once Chet has approved the format, it will be sent to the OASIS
> membership for a vote.
> 8. Admonitions
> Larry Rowland reviewed standards for admonitions. He suggests adding .
> The TC agree to add as a new admonition.
> The TC also discussed whether there should be an attribute that can be used to
> specify a particular standard for admonitions (e.g., ANSI or ISO). The TC decided
> that this should be strictly a stylesheet question and not part of the standard.
> Scott asked, what about safety instructions? This is an ANSI spec, but not ISO
> (at the moment; the two standards are being unified, which might cause this to
> be added to the unified spec).
> TC discussed whether to add a general element to cover cases
> such as safety instructions. This element would be the same as the others,
> except
> LexisNexis is a trading name of RELX (UK) LIMITED - Registered office - 1-3 STRAND, LONDON WC2N 5JR
> Registered in England - Company No. 02746621 

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]