Primarily parameters capture the data that accompany events.

However, the usage of parameters could be general in nature.  For example, for platforms that have dynamic object creation and life cycle management, these parameters could be used to represent dependant object as well as data keys.

For dynamic segment composition schemes, these parameters could be used to customize included segments at runtime.

The point here is that apart from event parameters, the general implementation implications of parameters would differ from platforms to platforms.

For events the id for the parameters descriptors would be registered against the event. For page composition, the parameters would have a parent, which would the segment that represents the included page.

The parameters descriptor could describe 1) an object that hold the properties that would be used as parameters, 2) or map object, or collection of objects that hold the key and value parameter pairs. 3) In addition, it could be a parent to one or more parameter descriptors.  The latter "parameter" singular descriptor, affords a finer grain parameter binding of individual key and value pair; whereas the "parameters" are bound to collection, or whole object.