Darrell O'Donnell, P.Eng. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: HAVE JIRA issues
WOW, great stuff Rex! We should be able to make great progress with your input here and let you sleep in a bit in the morning. I trust Robert will be able to make the document changes from here.
I’m reviewing/updating the SOU and working the 1.0. I’ll be on the call tomorrow and may have my bit ready as well.
From: rexbroo [mailto:rexb@starbourne.com]
Sent: Wednesday, August 2, 2017 8:22 PM
To: O'Connor, Robert <Robert.O'Connor@iem.com>; Darrell O'Donnell <darrell.odonnell@continuumloop.com >; Elysa Jones <elysajones@yahoo.com>
Subject: Re: HAVE JIRA issues
This took me 4.5 hrs total, but it should cut down tomorrow's work. I definitely do not volunteer to do this. The data dictionary was my contribution.
40-Add conformance clause in Section 5 of spec doc per Darrell's suggestion. follow example of EDXL-RM http://docs.oasis-open.org/
emergency/edxl-rm/v1.0/os/ EDXL-RM-v1.0-OS.doc 41-This should be marked resolved. It has been handled by the addition of the conventional data dictionary.
42-Move EDXL-DE to Non Normative References and make 'Non Normative References' a heading: e.g.1.3 Non Normative References
43-Mark as resolved, the reference in the current draft spec doc is correct
44-Mark as resolved. It has been handled in the data dictionary.
45-Appendix A should be removed as it has been superseded by the data dictionary. Mark as resolved.
46-I vote to reply "Declined"
47-Suggest following example Conformance Section of EDXL-RM http://docs.oasis-open.org/
emergency/edxl-rm/v1.0/os/ since the data dictionary now contains requirements and if we get this back from the Public Review I would decline to go into detail about requirements or else we'll be at this when hell freezes over.EDXL-RM-v1.0-OS.doc 48-Mark as resolved due to addition of conventional data dictionary.
49-I vote to decline with comment to commenter that we will decline in future too, if this is returned to us unless commenter cares to be specific about exactly what passages (Line numbers) are referred to in Section 3.5 that references Section 3.3 as if it is normative. In that case, I'd change the passage in Section 3.5 whatever it is.
50-Drop the unused references while moving EDXL-DE to Non Normative References.
51-Drop the unused references.
52-Use the recommended superseding references.
53-Use the recommended current citation
54-Use the recommended current citation
55-Use the recommended current citation
56-Be sure to delete the unused references first, then: Use the correct styling, but follow the tabular format already in use since the format that follows applies only to typestyle, not tabular format http://docs.oasis-open.org/
TChandbook/Reference/ WPQualityChecklist.html
EXAMPLE CITATION CONSTRUCTION:
[CITATION-LABEL]
Work Product title (italicized). Approval date (DD Month YYYY). Stage Identifier and Revision Number (e.g., Committee Specification Draft 01). Principal URI (version-specific URI, e.g., including the filename component with stage and revision: /somespec-v1.0-csd01.html ).
Two examples:
[CAP-1.2]
Common Alerting Protocol Version 1.2. 01 July 2010. OASIS Standard. http://docs.oasis-open.org/emergency/cap/v1.2/ .CAP-v1.2-os.html
[OpenDocument-1.2]
Open Document Format for Office Applications (OpenDocument) Version 1.2. 19 January 2011. OASIS Committee Specification Draft 07. http://docs.oasis-open.org/office/v1.2/csd07/ .OpenDocument-v1.2-csd07.html 57-We don't have any control over the html version of the spec. That is done by TC Admin, so we'll have to decline this and see if there are any broken links when the public review draft is produced for us.
58-I don't know what this is referring to. I vote to decline.
59-Correct ttp to http at what was line 1267
60-Check to be sure this reference isn't one of those to be deleted before correcting this link--this may require some time chasing down the correct link--but I bet it is one of those to be deleted.
61-Check to make sure this is not one of the references to be deleted and if not, Use the correct citation per the issue.
62-https://issues.oasis-open.
org/browse/EMERGENCY-62 This wasn't included in Robert's list, but we don't generate the pdf, TC Admin does, so we have to decline.63-We don't generate line numbers, TC Admin does that, so we should double check with TC Admin tto make sure that is done for the public review.
On 8/2/2017 12:31 PM, O'Connor, Robert wrote:
Hi, folks. There are 23 open issues in JIRA for HAVE. Most were created over two years ago - none have been updated since 2015.
Any ideas about where to start? Here they are, ordered by most recent Updated Date.
Issue Type
Key
Summary
Assignee
Reporter
Priority
Status
Resolution
Created
Updated
Due Date
Bug
Line Numbering in Document
Unassigned
Darrell O'Donnell
Major
New
Unresolved
11/10/2015 21:43
11/10/2015 21:43
Bug
Data Dictionary - Normative Content?
Darrell O'Donnell
Darrell O'Donnell
Major
New
Unresolved
6/2/2015 16:14
11/10/2015 21:31
Bug
Note in 5 Conformance
Unassigned
Darrell O'Donnell
Major
New
Unresolved
6/2/2015 16:10
11/10/2015 21:21
Bug
Requirements in Section 4 are unclear
Unassigned
Darrell O'Donnell
Major
New
Unresolved
6/2/2015 16:06
11/10/2015 21:19
Bug
References should be non-normative?
Unassigned
Darrell O'Donnell
Minor
New
Unresolved
6/2/2015 16:02
11/10/2015 21:16
Bug
None of the RFC keywords appear to be used
Darrell O'Donnell
Darrell O'Donnell
Minor
New
Unresolved
6/2/2015 16:00
11/10/2015 21:11
Bug
Stability of schema is unclear
Darrell O'Donnell
Darrell O'Donnell
Major
Closed
Unresolved
6/2/2015 16:08
11/3/2015 21:11
Bug
Bad reference for EDXL-DE
Darrell O'Donnell
Darrell O'Donnell
Major
Closed
Unresolved
6/2/2015 16:04
11/3/2015 21:09
Bug
Incorrect Reference
Darrell O'Donnell
Darrell O'Donnell
Major
New
Unresolved
6/2/2015 16:30
11/3/2015 21:06
Improvement
The specification does not seem to target EDXL-HAVE processors, unlike other EDXL specifications
Darrell O'Donnell
Darrell O'Donnell
Major
New
Unresolved
6/2/2015 15:57
11/3/2015 21:06
Bug
Unused Non-Normative References (11)
Darrell O'Donnell
Darrell O'Donnell
Major
New
Unresolved
6/2/2015 16:16
6/16/2015 20:08
Bug
Normative text?
Darrell O'Donnell
Darrell O'Donnell
Major
New
Unresolved
6/2/2015 16:15
6/16/2015 20:07
Bug
Conformance clause is vague
Darrell O'Donnell
Darrell O'Donnell
Major
New
Unresolved
6/2/2015 16:13
6/16/2015 20:05
Bug
Style variations in 1.2/1.3
Darrell O'Donnell
Darrell O'Donnell
Minor
New
Unresolved
6/2/2015 16:23
6/2/2015 20:42
Bug
Link Redirects (8)
Darrell O'Donnell
Darrell O'Donnell
Minor
New
Unresolved
6/2/2015 16:28
6/2/2015 20:42
Bug
Broken link (1)
Darrell O'Donnell
Darrell O'Donnell
Minor
New
Unresolved
6/2/2015 16:27
6/2/2015 20:38
Bug
Hanging Paragraphs
Darrell O'Donnell
Darrell O'Donnell
Minor
New
Unresolved
6/2/2015 16:26
6/2/2015 20:38
Bug
Styling of entries in references
Darrell O'Donnell
Darrell O'Donnell
Minor
New
Unresolved
6/2/2015 16:25
6/2/2015 20:37
Bug
Incorrect citation
Darrell O'Donnell
Darrell O'Donnell
Minor
New
Unresolved
6/2/2015 16:22
6/2/2015 20:36
Bug
Superseded reference
Darrell O'Donnell
Darrell O'Donnell
Major
New
Unresolved
6/2/2015 16:18
6/2/2015 20:34
Bug
Incorrect citation
Darrell O'Donnell
Darrell O'Donnell
Major
New
Unresolved
6/2/2015 16:21
6/2/2015 20:34
Bug
incorrect citation
Darrell O'Donnell
Darrell O'Donnell
Major
New
Unresolved
6/2/2015 16:20
6/2/2015 20:34
Bug
Unused Normative References
Darrell O'Donnell
Darrell O'Donnell
Major
New
Unresolved
6/2/2015 16:18
6/2/2015 20:33
Disclaimer
This e-mail and its attachments may contain privileged or confidential information. Please consult IEM before sharing this e-mail with anyone else. If you are not the intended recipient of this e-mail, you may not use, copy, distribute, or forward this e-mail. If you received this e-mail by mistake, please notify IEM and immediately delete this message. Although IEM does not know of any viruses present in this e-mail, you are encouraged to scan it using antivirus software, and IEM will not accept responsibility for any loss or damage arising from this e-mail. This e-mail neither constitutes an agreement to conduct transactions by electronic means nor creates any legally binding contract or enforceable obligation in the absence of a fully signed written contract. IEM takes no responsibility for any unauthorized reliance on the contents of this e-mail.
--Rex BrooksStarbourne Communications DesignEmail: rexb@starbourne.comGeoAddress:1361 Addison St. Apt. ABerkeley, CA 94702Phone: 510-898-0670
Attachment:
Draft EDXL-HAVE SC MeetingNotes 2017-08-03.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]