Inconsistent field name casing.

Ideally, fields would have a common naming convention. The specification currently uses multiple different casing methods in various parts of the spec. For example, the `documentationUrl` field under service information is camel case, while `creation_time` in the task definition is snake case. These should be unified in future versions.

Review the field definitions in the service information and task definition sections, especially `documentationUrl` and `creation_time`. First determine and document the naming convention the specification should adopt; completion requires an agreed convention and consistent field names in a future specification version.

Written by the indexing model from the issue text.