Re: [legalxml-courtfiling] Issues found while preparing ECF v4.01 CS01

[Chet Ensign <chet.ensign@oasis-open.org>]

Hi Jim, 

Well, here are the options as I see them... 

- You could produce another working draft with these non-material changes and request a Special Maj Vote to approve it as a CS with Non-Material changes. Then, once that is done and CS02 is published, hold the SMV to approve that as a COS

- Go to COS now, hold the 60 day public review and OS vote and then, assuming everything goes smoothly, deal with these as an Approved Errata afterwards. (We can discuss the specifics of how that would work.) 

- Produce a new CSD with these fixes, hold another 15-day PR then vote to approve the CS after that with the expectation that it would go to COS. 

My one concern with the 2nd option is that, if you hold the 60 day PR and then want to make changes, you have to go back to CSD and walk all the way up the food chain again, including another 60 day PR on the next COS. (The TC Process says that if you receive comments during the 60 review of the COS and you decide to make changes, you start with a new working draft and Commitee Spec Draft - basically, that you are start over.) 

If you think that the 60 public review is likely to produce comments, you may want to do another 15-day public review round now. 

/chet

On Thu, Dec 20, 2012 at 10:54 AM, James E Cabral <jcabral@mtgmc.com> wrote:

Paul,

 

Thank you for the clarifications.

 

Chet,

 

Would a valid approach be to address these minor issues after the public review?  If we assume that we will receive some substantial comments during the public review, we will probably need to issue another version as a result.

 

Jim Cabral
MTG Management Consultants, L.L.C.
www.mtgmc.com
(206) 442-5010 Phone
(502) 509-4532 Mobile

 

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: Paul Knight [mailto:paul.knight@oasis-open.org]
Sent: Thursday, December 20, 2012 6:51 AM
To: James E Cabral
Cc: Chet Ensign; legalxml-courtfiling@lists.oasis-open.org; anne.hendry@oasis-open.org
Subject: Re: [legalxml-courtfiling] Issues found while preparing ECF v4.01 CS01

 

Hi Jim and all,

 

A couple of additional notes below, regarding the references to OASIS documents.  I hope these recommendations will be included by the TC in the next revision.

 

Best regards,

Paul

On Thu, Dec 20, 2012 at 2:33 AM, James E Cabral <jcabral@mtgmc.com> wrote:

Chet,

See my analysis of the broken links below.  What would be the easiest way to apply these fixes before we move to Candidate OASIS Standard?  Do we need to issue another Committee Specification?

Jim Cabral
MTG Management Consultants, L.L.C.
www.mtgmc.com
(206) 442-5010 Phone
(502) 509-4532 Mobile

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.

-----Original Message-----
From: legalxml-courtfiling@lists.oasis-open.org [mailto:legalxml-courtfiling@lists.oasis-open.org] On Behalf Of Chet Ensign
Sent: Wednesday, December 19, 2012 7:29 AM
To: legalxml-courtfiling@lists.oasis-open.org
Cc: Paul Knight; anne.hendry@oasis-open.org
Subject: [legalxml-courtfiling] Issues found while preparing ECF v4.01 CS01

Members of the LegalXML Court Filing TC,

Congratulaions! The ECF v4.01 Committee Specification 01 has been published.

In preparing the CS, we came across some issues in the content. I'm passing them along to you in case you want to fix these before advancing the CS to Candidate OASIS Standard.

* We found 11 broken links in the CS:

In Normative references:

- [Genericode]  A. B. Coates, Code List Representation (Genericode) 1.0, http://docs.oasis-open.org/codelist/ns/genericode/1.0/, OASIS Committee Specification, December 28, 2007

This link is valid.

The link is valid, but it points to the namespace document rather than to the specification itself.  A better link would be to the specification:

Code List Representation (Genericode) Version 1.0. 28 December 2007. OASIS Committee Specification 01. http://docs.oasis-open.org/codelist/cs-genericode-1.0/doc/oasis-code-list-representation-genericode.html.

- [NIEM Techniques]  Techniques for Building and Extending NIEM, http://www.niem.gov/topicIndex.php?topic=techPDF, Georgia Tech Research Institute, August 2007.

This has changed to http://reference.niem.gov/niem/guidance/techniques-for-building-and-extending/2.0.1/techniques-for-building-and-extending-niem-2.0.1.pdf.

In Non-Normative references:

- [Juvenile XML]  S. Rondendell, et. al., Juvenile Justice XML Report, http://www.ijis.org/db/share/public/Library/Publications/juvenile%5fjustice%5fxml%5ffinal%5freport%5f20050630.pdf, IJIS Institute,

This has changed to http://www.kms.ijis.org/db/share/public/Library/Publications/juvenile_justice_xml_final_report_20050630.pdf.

- [SOA-RM]  MacKenzie, et al., Reference Model for Service Oriented Architecture 1.0, http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=soa-rm, OASIS Public Review Draft 1.0, February 10, 2006.

This link is valid.

Again, the link itself is valid, but it simply points to the TC's main web page instead of the document. 

The reference using the OASIS citation format would be:

Reference Model for Service Oriented Architecture 1.0. 12 October 2006. OASIS Standard. http://docs.oasis-open.org/soa-rm/v1.0/soa-rm.html

- [Traffic IEPD]  Traffic Citation IEPD, http://www.ncsconline.org/d_tech/gjxdm/iepd/citation/Traffic_Citation_08_08_2005.zip, National Center for State Courts, August 8, 2005.

This has changed to http://www.ncsc.org/about-us/committees/joint-technology-committee/~/media/Files/PDF/About%20Us/Committees/JTC/Traffic%20Citation%20IEPD%20Final.ashx.

In section 2.4.4

- <CaseOfficialRoleText> - /legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/cs01/gc/ECF-4.0-CaseOfficialRoleCode.gc

This link should be gc\ECF-4.0-CaseOfficialRoleText.gc.

In section B.3.

- Citation Filing Model - model/uml/html/Violation Filing.png

- Extended Person Information Model - model/uml/html/ExtendedPersonInformation.png

- Review Filing Model - model/uml/html/ReviewFiling.png

These 3 links should be removed

In Appendix D.

- CoreFilingMessage (Criminal case type) - xml/ECF-4.0-CoreFilingMessage-Criminal.xml

This file should be renamed from ECF-4.0-CoreFilingMessage-Criminal2.xml  to ECF-4.0-CoreFilingMessage-Criminal.xml

- MessageReceiptMessage - xml/ECF-4.0-MessageReceiptMessage.xml

This link should be removed

* In section 1.3 ECF Version 4.01, the last sentence of the first paragraph is "Relationship to other XML Specifications."
It looks like this was intended to be section 1.4. As currently formatted, it looks like the following sections (e.g. 1.3.1 National Information Exchange Model (NIEM)) are subheads of 1.3 ECF Version 4.01.

Relationship to other XML Specifications should be a heading numbered 1.3.1.  The existing 1.3.1 - 1.3.5 should be renumbered to 1.3.2 - 1.3.6.

* In appendix A5. Known Errata, the link for the TC's webpage points to the restricted Kavi link http://www.oasis-open.org/apps/org/workgroup/legalxml-courtfiling/ instead of to its publicly visible version http://www.oasis-open.org/committees/legalxml-courtfiling/. Non-OASIS members will not be able to get to this link.

This link should be http://www.oasis-open.org/committees/legalxml-courtfiling/.

* The links to NIEM (Related links on the cover page, Normative References) point simply to the niem.gov, not to a specific NIEM document or specification. Is there some more specific location to which readers could be directed?

The NIEM PMO moves these things around all the time.  It is probably safer to just point to niem.gov.

We hope that you find this useful as you continue to work on the specification. Let me know if you have any questions.


/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

---------------------------------------------------------------------
To unsubscribe, e-mail: legalxml-courtfiling-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: legalxml-courtfiling-help@lists.oasis-open.org

 

--
Paul Knight  - Tel: +1 781-861-1013
OASIS - Advancing open standards for the information society
Document Process Analyst

--

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open