Fix Type for optional, oneOrMore and zeroOrMore in Patterns Table

[FeLungs]

Filing an issue about the xAPI Profiles specification? Please include the following

Which part/parts of the specification are at issue?

type column value for optional, oneOrMore and zeroOrMore

Given above, optional, oneOrMore and zeroOrMore must be defined as

• {"id": "Pattern URI" | "Template URI"}

but alternates and sequence must be defined as

• ["Pattern URI" | "Template URI", "Pattern URI" | "Template URI", ...]

ideally, all pattern items should be either a URI or an Array of URI

• no need to wrap the single URI in an Object when the only field is id
  • doesn't add any additional information
• alignment with examples in the spec
  • see screenshots below

What is your understanding of what the spec means in these parts?

Reference to "A single Pattern or Statement Template identifier"

oneOrMore

zeroOrMore

Related to your implementation, what's the use case you're trying to achieve? What are the user stories you're trying to support?

Removal of unnecessary Object container

How you would like the specification to be improved?

Replace object with URI for optional, oneOrMore and zeroOrMore

Property	Type	Description	Required
optional	URI	...	...
oneOrMore	URI	...	...
zeroOrMore	URI	...	...

@aaronesilvers, @andyjohnson this issue relates to validation of xAPI Profiles against the spec.

• Correction of the inconsistencies will reduce confusion for
  • Spec readers
  • Profile Authors
  • Profile Validation devs

[creighton]

Agree they should be URI, also note the description for the id field should say "A URI for the Pattern"

[andyjohnson]

Per the 7/19/2022, group agrees- feel free to throw a PR at this (or I could too)

[andyjohnson]

Per the 7/19/2022 - would like to see some solid pattern examples with some logic/flow graphical support

[andyjohnson]

Per the 7/19/2022 - can use https://github.blog/2022-02-14-include-diagrams-markdown-files-mermaid/ to create flow within Markdown