Updates the ML prediction pipeline example according to the latest discussion on the profile:
record image formats via encodingFormat
link workflow inputs to action objects and workflow outputs to action results via exampleOfWork
remove additionalType entry from PropertyValue entitites (that info can now be retrieved by following exampleOfWork to the corresponding FormalParameter)
File parameters now list their expected format via encodingFormat, while additionalType has been changed to ImageObject. Note that I haven't added an encodingFormat entry to non-file parameters (e.g., integers): would it make sense to do so? E.g., text/plain?
Updates the ML prediction pipeline example according to the latest discussion on the profile:
encodingFormatexampleOfWorkadditionalTypeentry fromPropertyValueentitites (that info can now be retrieved by followingexampleOfWorkto the correspondingFormalParameter)File parameters now list their expected format via
encodingFormat, whileadditionalTypehas been changed toImageObject. Note that I haven't added anencodingFormatentry to non-file parameters (e.g., integers): would it make sense to do so? E.g.,text/plain?