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] First cut at DocBook spec


Please list my association as Pelco by Schneider Electric.

I also agree with the “should” wording for identifying DocBook documents and schemas.

Thanks and best regards,

--Scott
Scott Hudson   |   PELCO  by Schneider Electric   |   United States  |   Standards & Information Architect 
Phone:
 +1 970 282 1952  |  Mobile: +1 720 369 2433 
 | Email: scott.hudson@schneider-electric.com


On Apr 24, 2014, at 9:59 PM, Nancy Harrison <nharrison@infobridge-solutions.com> wrote:

Hi,

Just a couple of comments:

1. Dick is right about my being an 'individual' at this point, from OASIS's point of view.  Also, I believe that Gershon is at Cisco, and Scott is with some subsidiary of SAS.  And Arbortext doesn't exist any more, So Paul is either at PTC or unaffiliated.

2. I agree with Dick wrt '3. Identifying DocBook Documents and Schemas'  Using 'can' is ambiguous; it implies that using some other notation would be just as good.  But users would be served better if we give them some guidance and encouraged consistency, so I think 'should' would be better.

regards,
Nancy



_____________
Nancy Harrison
Infobridge Solutions 
nharrison@infobridge-solutions.com


On Thu, Apr 24, 2014 at 6:11 PM, Richard Hamilton <hamilton@xmlpress.net> wrote:
Hi Norm,

Here are a few notes from my quick read-through of the spec:

1) You've got some un-resolved macros (e.g., {TC name | membership of OASIS} {short name}, etc.)

2) 1.1 Terminology: are key words always italicized? If so, I would change the last sentence to read something like: When used as key words, these words are always italicized. Any instances that are not in italics are not to be interpreted as key words. Note that for reasons of style, these words are not capitalized in this document.

3) 3. Identifying DocBook Documents and Schemas: in the second paragraph, should the second instance of the word "can" be replaced with a key word? Possibly "should"?

4) A. The DocBook Media Type, Security considerations: Is this "should" a key word? Or is this a non-normative section, anyway, since it's an appendix?

5) A. The DocBook Media Type, Applications which use this media type: remove the comma after World Wide Web.

6) B. Acknowledgements: I'm guessing here, but I'll bet Steve Cogorno has a new affiliation (does Sun Micro exist anymore?) and I'm pretty sure Nancy Harrison also has a new affiliation (or perhaps is an Individual member).

Best regards,
Dick
-------
XML Press
XML for Technical Communicators
http://xmlpress.net
hamilton@xmlpress.net



On Apr 24, 2014, at 5:23 PM, Norman Walsh wrote:

> Hi folks,
>
> I think the last major stumbling block to publishing 5.1 is that we
> have to have a spec document for it. The whole toolchain that built
> the 5.0 spec seems to be in a shambles (no one's fault but my own, I
> don't do XSLT 1.0 anymore).
>
> So I hacked at it a bit. Here's my first cut. Still needs work but
> maybe starting to get there. Comments, etc. most welcome.
>

>
>
>                                        Be seeing you,
>                                          norm
>
> --
> Norman Walsh <ndw@nwalsh.com>      | There has never been a perfect
> http://www.oasis-open.org/docbook/ | government, because men have
> Chair, DocBook Technical Committee | passions; and if they did not have
>                                   | passions, there would be no need
>                                   | for government.-- Voltaire




---------------------------------------------------------------------
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


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________



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