We have received lots of complaints about the acronym "BKPMN" from a lot of sources. The name is hard to remember, hard to pronounce, breaks the 4-letter acronym pattern, and can be confused with BPMN. It can also easily be misspelled as seen in several parts of the spec and even in this issue description.

This issue will collect all the typos and resolve them in one issue for Ballot 1.

The acknowledgement section contains information from the RFP, but not the FTF

Update copyright section
Update the years of contribution based on OMG-recognized contributors and taskforce membership.

The current BKPMN XSDs were developed with a faulty translation of UML class relationships to the XSD elements.
To resolve this issue we need to specify the XSD patterns that correspond to the UML class relationships and then update the XSDs.

OperationalDocumentRef properties are mismatched between the metamodel diagrams, the descriptive table, and the XSD

BKPMN has a lot of metadata intended to provide information about the contents of the package (i.e., the label on the box). All the metadata elements should be reviewed with the goal of simplifying the V1.0 version of the spec and to include only the essential metadata.

And to make clear that Parties is a component of the knowledge package.