A proxy server that acts as an Efiling Service Provider, connecting guided interviews to Efiling Managers on Tyler Technologies implementation of ECF 4.0
The docs are (surprise surprise!) ambiguous about this one. Nothing in the reference guide says anything about it, but the GetPolicyMessage has a urlattachmentSupportedIndicator. Which isn't exclusively saying that courts expect a URL, just that they support one.
The ECF spec mentions attachments, which seems like a restatement of MTOM, but either way says that the
actual binary encoded electronic document SHOULD be included in ore or more attachments to the message or MAY be embedded in the message using following structure (...</...>)
So we've got the correct default implementation there.
The docs are (surprise surprise!) ambiguous about this one. Nothing in the reference guide says anything about it, but the GetPolicyMessage has a urlattachmentSupportedIndicator. Which isn't exclusively saying that courts expect a URL, just that they support one.
The ECF spec mentions attachments, which seems like a restatement of MTOM, but either way says that the
So we've got the correct default implementation there.
The URL download option is mentioned in http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/errata02/os/ecf-v4.01-spec-errata02-os-complete.html#_Toc425241596, which says that the indicated development policies aren't likely to change from the development stage, and again is vague on if the court is only accepting URL downloads. None of the current IL courts have the URL attachment policy on at this point, so I don't think we need to support URL downloads from the proxy server.