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

 


Help: OASIS Mailing Lists Help | MarkMail Help

coel message

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

Subject: Rough agenda for today's call

Folks,

 

I suggest we go through the two mails containing comments from the PC that we have and see if any are substantial enough to require another round of review or if we think they can just be called ‘cosmetic’.

 

I have attached these to this mail.

 

--

Take care:

    Dr. David Snelling < David . Snelling . UK . Fujitsu . com >

    Senior Research Fellow / Fujitsu Distinguished Engineer

    Fujitsu Laboratories of Europe Ltd.

    +44-7590-293439 (Mobile)

 

 


Unless otherwise stated, this email has been sent from Fujitsu Services Limited (registered in England No 96056); Fujitsu EMEA PLC (registered in England No 2216100) both with registered offices at: 22 Baker Street, London W1U 3BW; PFU (EMEA) Limited, (registered in England No 1578652) and Fujitsu Laboratories of Europe Limited (registered in England No. 4153469) both with registered offices at: Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE.
This email is only for the use of its intended recipient. Its contents are subject to a duty of confidence and may be privileged. Fujitsu does not guarantee that this email has not been intercepted and amended or that it is virus-free.
--- Begin Message --- 
Greetings!

Members of the Technical Advisory Board endeavor to comment on all 30
day public review drafts.

Comments on:

Classification of Everyday Living Version 1.0

Roles, Principles, and Ecosystem Version 1.0

Behavioural Atom Protocol Version 1.0

Minimal Management Interface Version 1.0

Identity Authority Interface Version 1.0

Public Query Interface Version 1.0

are attached.

It isn't necessary to acknowledge each comment separately.

A single email acknowledging this email will be sufficient.

If the TC chooses to ?defer? resolution of an issue to a later
version, please choose Defer Issue under Available Workflow Actions
(after opening the issue).

When the TC has acted on these issues, I would appreciate a pointer to
the TCs resolution as the TAB is tracking the resolution of comments
from TAB members.

Hope everyone is at the start of a great weekend!

Patrick

-- 
Patrick Durusau
patrick@durusau.net
Technical Advisory Board, OASIS (TAB)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau

Attachment: COEL-9December2016.xls
Description: MS-Excel spreadsheet

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Members of the COEL TC, 

In preparing your content for public review, we encountered the following items that we bring to your attention. 

- In all files, we noted several instances of tables with cells where the text is fully justified on both sides. In the HTML, this introduced extra spacing and interfered with readability. You might consider changing the paragraph style on these cells to be left-justified.

- Behavioural Atom Protocol, in section 2, there are references in the text to [HTTP] and [JSON] that link directly to the specs and that also are not listed in the References section. 

Any specifications listed in the body of the text must also be listed in the References section as either Normative references or Non-Normative references and must link to those specs from there. Typically, by linking from these text entries back to your references section, you have only one place to update references when they change. 

- Behavioural Atom Protocol, in section 4, Conformance, the reference to [COEL_RPE-1.0] in the text does not link back to the Normative references entry.

- Identity Authority Interface, on our copy, the header H1 style was corrupted. The section numbers didn't appear in the HTML and on the PDF there was just a black box. You may want to use our copy of the docx file for the next round of edits. 

- Rules, Principles, and Ecosystem, in the table you use of the specific font type for symbols didn't work well in the HTML. 

The symbols are in "Wingdings". In HTML, they did not display properly in the Firefox browser. In Chrome they looked ok. I did not check with Safari or IE. 

We recommend using "Arial Unicode MS"  and the following characters:

    HEX     DECIMAL
✓ = 2713 or 10003
✔ = 2714 or 10004
✗ = 2717 or 10007
✘ = 2718 or 10008

Let us know if you have any questions. 

Best regards, 


--

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

--- End Message ---

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