JobAnnotation is intended to contain machine processable content, in contrast to Description. JSDL documents may be transformed or refined by multiple entities before execution and JobAnnotation was provided to support the addition of information (like unique identifiers) that may be useful to some but not all entities. The content of each JobAnnotation may be substantially different so concatenating into a single string would make processing more difficult. At least that was the original idea. We later fully embraced an open content model (xsd:any##other) so the use of this element is not really necessary. We are now working on an errata release of JSDL 1.0, and this was one of the issues posted. An errata release is expected to have text discouraging the use of this element. You might like to have a look at the JSDL 1.0 errata tracker: https://forge.gridforum.org/sf/tracker/do/listArtifacts/projects.jsdl-wg/tra... Andreas Nicholas Loulloudes wrote:
Hello,
As i read in the JSDL schema specification, JobAnnotation under JobIdentification is an attribute of type=string that can be utilized by the user to describe a job and additionally can also be used by the consuming system.
Since, this attibute is of type = string, could you tell me the reason for the unbounded max. occurrence's?
Thank you in advance.
-- Andreas Savva Fujitsu Laboratories Ltd