Actuator Profile Subcommittee,
At the last monthly meeting, the Technical Committee tasked the editors of the specifications to assist in planning the agenda for the Face to Face. The scope of the tasking is to provide a listing of the comments to be resolved and approximate time
required for discussion.
REQUEST: Please comment on the topics and time estimates for the Face to Face agenda. It would be especially beneficial if you could look at the CRM spreadsheet and github issues and provide comments in advance.
PROPOSED Actuator Profile Agenda: (Bottom Line Up Front: )
Actuator Profile Subcommittee Public Review Comments:
- Conformance Section (45 minutes)
- Refer to Language Specification Discussions (30 minutes)
- Relation to other specifications (15 minutes)
- Mechanical/ non-material (10 minutes)
Actuator Profile Subcommittee Way Forward:
- Scope/ Breadth of Profiles (20 minutes)
- Committee Note: Actuator Profile Writing Guide (10 minutes)
- Future Profiles (10 minutes)
Here is my logic or lack thereof to come up with the proposed agenda:
Please refer to the spreadsheet and/or the flurry of emails I sent out over the past couple days.
The following issues are 'mechanical' in nature. That is to say, they involve typos, wording, cross checking references etc. I estimate that the following issues will take less than ten minutes each to resolve and consensus via email would be ideal.
I would like to allocate approximately 15 minutes at the F2F. This is achievable if we can agree on most of these via email.
- Modify the examples in Annex C to include a direction argument and add prose explaining why the actuator field (without specifiers) may be populated. (SLPF-1 and 2)
- Generate a Table of Contents for the MD version of the specification. The Language SC is looking into a way to do that automatically. (SLPF-3)
- Correct grammatical, typographical and table corruption errors. (SLPF-7, 10, 11 and 16)
- Cross check references to verify if normative or non-normative (SLPF-8)
- Label sections as normative or non-normative. (SLPF-17)
- Create hyperlinks where appropriate (SLPF-9)
The following issues actually impact the Language Specification. I believe we can resolve these quickly, but the actual resolution is subject to how a related issue in the Language specification is resolved. I would like to allocate 30 minutes at the
F2F. We will need some time to determine the best way to incorporate, but much of this will be influenced in the language spec discussions, so it seems logical to avoid redundancy.
- Document semantics for common arguments in the Language Specification and simply reference in the SLPF. (SLPF-5)
- Support ranges of IP addresses, that is include the ip_net target. (SLPF-6)
- Compliance should map to the schema, not property tables (SLPF-4)
- JADN as normative (SLPF-19)
The following issues pertain to how the documents relate to the Actuator Profile. I would like to allocate 15 to 30 minutes at the F2F.
- References to the Language Specification. Version 1.0 or higher? Or simply Version 1.0 (SLPF-12 and 25)
- Need a section on transport (SLPF-18)
The following issues relate to the conformance section of the specification. I would like to allocate 45 minutes at the F2F
- Create an Annex for the traceability matrix and the supporting information for the conformance section (SLPF-13 and 14)
- Create more conformance clauses (SLPF-23 and 15)
The following issues were identified prior to the Public Review, but were not closed. I would like to allocate 30 minutes at the F2F
- Validity of the 'Update' use case (SLPF-20)
- Error responses (SLPF-21)
- Profile scope and breadth (SLPF-24)
Thank you
VR
Joe Brule
Engineering (Y2D122)
FNX-3, B4A335
410.854.4045
'Adnius ad retinedam puritem noster peciosus corporalis fluidorum…'