Edits to the googledoc

["Brule, Joseph M" <jmbrule@radium.ncsc.mil>]

All, 

I am attempting to stick the proverbial fork in the SLPF and would like to do a call for objections on the following:  

ONE:  Front Matter:  Look on page three of the SLPF or look at https://docs.google.com/document/d/1UE2v84sUUD25VTYgmsqWJA4JARxyplA85n7UOSCQ6Tw/edit to see the front matter all three of the draft specifications.    

Please note, I added the phrase "Cyber defense components, devices, systems and/or instances may (in fact are likely) to implement multiple actuator profiles..."  Then the last sentence in section 1.1 I added "Though Ccyber defense components, devices, systems and/or instances may implement multiple  may implement multiple actuator profiles, a particular OpenC2 message may at most reference a single actuator profile.  The scope of this document is limited to SLPF. "

TWO:  Three to 40 characters for a property name (vice 250 characters) 

THREE:  Document Overview (section 1.4 on page 10 of the SLPF).  
Did not know what else to do with it so stated the scope of each section

FOUR:  Acks.  I wrote the following: 
"The Actuator Profile Subcommittee was tasked by the OASIS Open Command and Control Technical Committee (OpenC2 TC) which at the time of this submission, had 132 members.  The editor's wish to express their gratitude to the members of the OpenC2 TC. 
The following individuals are acknowledged for providing comments, suggested text and/or participation in the SLPF CSD ballots: "

FIVE:  
Addition of 'asset_tuple' as a specifier (page 18) 

SIX:  
Seeking help on the conformance section...

VR

Joe Brule