[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: ECF v4.0 Specification Feedback
|
ECF TC: Open Networks, who was selected by the Springboard initiative to develop the ECF conformance testing framework, has provided some feedback (potential issues
and/or questions) about the ECF 4.01 core and web service SIP specifications. I will add this feedback to the agena for discussion at the face to face next Friday. Please review these in advance of the meeting and contribute any suggested responses to the
email list. Thanks, Jim Cabral Helping our clients make a difference in the lives of the people they serve. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you
received this in error, please contact the sender and delete the material from any computer. From: Scott Serich [mailto:Scott.Serich@ijis.org]
Jim & Jim – As promised, here’s the 1st list of potential shortcomings in the specification. I believe the fixes would all fall into the category
of “minor,” and I’ll leave it to your discretion whether we share any of this information with the Springboard ECF Initiative Team or not. Of course, we’ll also defer to your discretion regarding whether and how to present this information to the OASIS ECF TC. Do they have some way to issue errata
perhaps? Our work on the Springboard ECF Test Harness will continue as planned. I’ll send the 2nd list shortly… From: Todd Seymour [mailto:seymour.todd@gmail.com]
We started the ECF v4.0 Specification review and Springboard implementation with the following specification links:
Electronic Court Filing Version 4.01 (ECF v4.01)
Electronic Court Filing 4.0 Web Services Service Interaction Profile Version 2.01 (ECF v4.0 WS SIP 2.01)
http://www.oasis-open.org/committees/download.php/43733/ecf-v4.0-webservices-v2.01-csprd02.zip
As such, the following observations/comments are based on our experience working with the above referenced specifications/packages.
·
The wsdl files provided in the ECF v4.0 WS SIP 2.01 package are not clearly linked to the schema files contained in the ECF v4.01 package.
o
Note:
§
we noticed 2 loose references to the relationship (wsdl to xsds) in the WS SIP document:
·
On page 1 of the ECF v4.0 WS SIP 2.01 document, the “Related work:” section provides a reference to the overall Electronic Court Filing Version 4.0 specification. While
the underlying link opens a specification that contains schema files, the link is not obvious. In addition, the link is not available if reviewing the “document” in the PDF version.
·
On page 8 of the ECF v4.0 WS SIP 2.01 document, the “Message” section states that “Information transmitted between MDEs that consists of a well-formed XML document that
is valid against one of the defined message structure schemas in the ECF 4.0 specification.”
o
Suggestion:
§
Provide the schemas in the ECF v4.0 WS SIP 2.01 package so that an implementor is able to open the wsdl and validate without having to first search for the associated
schemas and build a structure consistent with the wsdl’s relative schema paths.
§
Alternatively, embed a metadata or readme file in the ECF v4.0 WS SIP 2.01 package that accompanies the wsdl files and clearly directs the reader/implementor to the schemas.
·
The schemas included in the ECF v4.01 package have an inconsistency in the UBL schema namespace/reference which prevents complete validation of the wsdl.
o
Notes:
§
The ECF-4.0-FeesCalculationResponseMessage.xsd file contains a schema import that links the "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
namespace with version 2.0 of the associated schema.
§
The ECF-4.0-PaymentMessage.xsd and the ECF-4.0-PaymentReceiptMessage.xsd schemas assign the same namespace to version 2.1 of the associated schema.
o
Suggestion:
§
Verify the version of the correct file for the "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" namespace.
§
Ensure the wsdl and associated schemas will validate.
·
The ECF v4.0 WS SIP 2.01 document references an older version (4.0) of the ECF specification.
o
Note:
§
On page 1 of the ECF v4.0 WS SIP 2.01 document, the “Related work:” section provides a reference to the overall Electronic Court Filing Version 4.0 specification
§
The latest version of the ECF specification, however, appears to be version 4.01.
o
Suggestion:
§
Provide clarification regarding which version(s) of the ECF specification are acceptable for the ECF v4.0 WS SIP 2.01.
·
The constraint schemas included in the ECF v4.01 package do not open in <oXygen/> XML Developer v14.1.
o
Notes:
§
Upon opening the files, <oXygen/> XML Developer reported “Bidirectional Text Detected.”
·
Example: “The document
http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.0/ecf-v4.0-spec/xsd/constraint/niem/ansi-nist/2.0/ansi-nist.xsd contains characters from the BIDI Unicode range or its orientation was changed.”
§
Altova XML Spy opened the files without an issue.
§
Once the files were opened and resaved, using either XML Spy or Notepad, then <oXygen/> XML Developer was able to open the files.
o
Suggestion: N/A .. FYI only
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]