legalxml-courtfiling — archive

[System]

Title: Message Hi, Steven, Glad you found the proposal worthy. The incrementing of a filename from 00 to 01 to 02... (not version number, which applies to specifications themselves, not the filenames of other documents) would be a reflection of just about any changes that are made short of the insignificant (correcting a capitalization error). The filename for a specification would not only contain the OASIS- or CS-, etc., prefix, it would be numbered to match the specification's version number. If the version were 2.1.2, the filename would end in -020102.xml. Thus, double-digits for things like statements of work or white papers, and 6-digit renderings of the version numbers of a specification. The other elements of a filename may or may not apply, depending on what kind of document is contained in the file. A specification could end up with an OASIS-LegalXML-ECF-CourtFiling-030101.xml filename, but no White Paper would ever have an OASIS- prefix, since we would not seek OASIS adoption of such a work product as an OASIS Standard. I tried to show how the various prefixes might be used, but not together, by not allowing one to have a - before the [    ] unless it is allowed as the 2 nd or subsequent part of the filename. Thus [CS]- shows a filename can start with this if it is an OASIS Committee Specification (=Legal XML's Recommended Specification ), but not [INFO-DRAFT]- since that indicates a different type of document is in the file it names. Please let me know if you have further questions. I'm copying this to the Technical Committee list, so others can see this exchange. Regards, Roger Roger Winters Electronic Court Records Manager King County Department of Judicial Administration 516 Third Avenue, E-609 MS: KCC-JA-0609 Seattle, Washington 98104 V: (206) 296-7838 F: (206) 296-0906 roger.winters@metrokc.gov