--
You received this message because you are subscribed to the Google Groups "ihe-xdw-implementors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ihe-xdw-implemen...@googlegroups.com.
To post to this group, send email to ihe-xdw-im...@googlegroups.com.
Visit this group at http://groups.google.com/group/ihe-xdw-implementors.
For more options, visit https://groups.google.com/groups/opt_out.
This should be annotated !!!
Charles
Hello Mauro,Thank you for specifying the correct schema.As I realized the main difference between the old and the new schema is the definition and usage of the “tXDSregisteredDocument” element.The XDW supplement (page 39) specifies the followings:“The taskData/input shall contain a taskData/input/part for every clinical document that isto be used as input to the task. This shall be an element of type tXDSregisteredDocument….”And“The element type tXDSRegisteredDocument is a tAttachmentInfo that hasXDSDocumentEntry.uniqueId as the attachmentInfo/identifier and anattachmentInfo/accesstype of "urn:IHE:iti:2011:xdw:XDSregistered"….”As I can conclude from the above text the “part” in the “taskData/input/part” is an element of type “tXDSregisteredDocument” and the “tXDSRegisteredDocument is a tAttachmentInfo” so the result is that “part” == (or kind of..) “tAttachmentInfo”When I checked that assumption in the ws-humantask-types.xsd I saw that “tAttachmentInfo” is not “part” so I assumed that there was a mistake in my assumption.Can you resolve the confusion based on the supplement text and the schemas: XDW-2012-12-19.xsd ws-humantask-types.xsd.In addition to the above can you specify if the WorkflowDocument xml example in page 45 (section 5.4.4 Complete Example) is a valid example, That I can refer too?In addition I would like to ask if you can specify a location: site or ftp site, that I will be able to see more such validated examples as a reference?Thanks a lot,Gil