[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: ECF 5 working draft 06
Gary, See the new language below. I added “valid” to the URL I also added the idea that a court-provided code list SHOULD (not MUST) be a superset of the specification-provided code list. ---- The specification provides non-normative [Genericode]
code lists for each of the XML elements in the above table. The specification-provided code lists in the table above that are marked as “Yes” for “Default Values” have specification-provided values. For each XML element, a court MAY either use the specification-provided
code list as its court-specific code list, or provide a court-provided [Genericode]
code list for that element. The values of any court-provided code list SHOULD be a superset of the values in the corresponding specification-provided code list. All court-specific lists MUST be itemized in court policy. When itemized in court policy, a policyresponse:RuntimePolicy/policyresponse:CodeListExtension element MUST be included for each list. The latest version and valid URL of all itemized court-specific lists MUST be defined using the policyresponse:ExtensionCanonicalVersionURI and policyreponse:ExtensionLocationURI elements, respectively. The following is a non-normative example of a reference to a code list in court policy: <policyresponse:RuntimePolicy> … <policyresponse:CodeListExtension> <nc:DocumentIdentification> <nc:IdentificationID>AbuseNeglectAllegationCategoryText </nc:IdentificationID> </nc:DocumentIdentification> <policyresponse:ExtensionCanonicalURI>https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.0/AbuseNeglectAllegationCategoryText</policyresponse:ExtensionCanonicalURI> <policyresponse:ExtensionCanonicalVersionURI>https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.0/AbuseNeglectAllegationCategoryText/2017-02-04</policyresponse:ExtensionCanonicalVersionURI> <policyresponse:ExtensionLocationURI>https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.0/AbuseNeglectAllegationCategoryText</policyresponse:ExtensionLocationURI> </policyresponse:CodeListExtension> … </policyresponse:RuntimePolicy> For any court-specific lists not itemized in court policy, then any value MUST be considered acceptable for the corresponding XML element. Similarly, if a court policy references a specification-provided or court-provided code list that does not include any values, then any value MUST be considered acceptable for the corresponding XML element. __ From: Graham, Gary Well then I suggest we include some guidance or even a requirement in the specification that
policyreponse:ExtensionLocationURI must contain a valid URL that references the location of the [Genricode] list. From: James E Cabral [mailto:jec@mtgmc.com] Thanks - I’ll replace that section with your language. With regard to URI or URL, those element names are defined by the NIEM Code List Specification so let’s stick with URI. __ From: Graham, Gary P.S. Perhaps one final clarification. The specification refers to a URL, whereas the element is a URI, i.e.
I presume the purpose for the
policyreponse:ExtensionLocationURI element is to locate the gc file. So should this element be
policyreponse:ExtensionLocationURL instead? From: James E Cabral [mailto:jec@mtgmc.com]
Your summary looks correct to me. Would simply replacing the current language with your language make it clearer? __ From: Graham, Gary Okay, here is what I think is being said in these two paragraphs:
From: James E Cabral [mailto:jec@mtgmc.com]
Gary, Would an example help illustrate? How about this The “default values” in the above table column indicates whether the
[Genericode] code list provided in the specification includes non-normative default values. If a court does not reference a court-specific code list for any of the following XML elements in court policy, then any value MUST be considered acceptable for
the corresponding XML element. Court policy MUST include a
policyresponse:RuntimePolicy/policyresponse:CodeListExtension element for each court-specific code list. The latest version and URL of all court-specific code lists MUST be defined using the
policyresponse:ExtensionCanonicalVersionURI and
policyresponse:ExtensionLocationURI elements, respectively. The following is a non-normative example of a reference to a code list in court policy: <policyresponse:RuntimePolicy> … <policyresponse:CodeListExtension> <nc:DocumentIdentification> <nc:IdentificationID>AbuseNeglectAllegationCategoryText </nc:IdentificationID> </nc:DocumentIdentification> <policyresponse:ExtensionCanonicalURI>https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.0/AbuseNeglectAllegationCategoryText</policyresponse:ExtensionCanonicalURI> <policyresponse:ExtensionCanonicalVersionURI>https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.0/AbuseNeglectAllegationCategoryText/2017-02-04</policyresponse:ExtensionCanonicalVersionURI> <policyresponse:ExtensionLocationURI>https://docs.oasis-open.org/legalxml-courtfiling/ns/v5.0/AbuseNeglectAllegationCategoryText</policyresponse:ExtensionLocationURI> </policyresponse:CodeListExtension> … </policyresponse:RuntimePolicy> BTW, this snippet comes from the policyresponse.xml example message which also includes references to other code lists as well. __ From: Graham, Gary In re: item 6 in the original attachment: Section 5.2.2 Court-Specific Code Lists
I am having some trouble understanding what is being said here beneath the table. It states:
The “default values” in the above table column indicates whether the
[Genericode] code list provided in the specification includes non-normative default values. If a court does not reference a court-specific code list for any of the following XML elements in court policy, then any value MUST be considered acceptable for
the corresponding XML element.
However no XML elements appear to be listed. Immediately following the above paragraph, there is: The default values are provided in the Genericode file referenced in the “Genericode code list” column, not in the written specification
Court policy MUST include a
policyresponse:RuntimePolicy/policyresponse:CodeListExtension element for each court-specific
code list. The latest version and URL of all court-specific code lists MUST be defined using the
policyresponse:ExtensionCanonicalVersionURI and
policyreponse:ExtensionLocationURI elements, respectively.
Is this ‘CodeListExtension’ element the only element in the list referenced in the first paragraph, or is the list absent and the second paragraph is unrelated to the prior paragraph? Implementations are required to reference court-specific code lists in Court Policy (the response to a GetPolicy operation). This paragraph defines the required elements in Court policy that reference
each court-specific code list. I understand that suggested values (you call them default values) are provided in a separate gc file. For example, FiducuaryTypeCode.gc provides four suggested values: ‘Conservator of the estate’, ‘Conservator
of the person’, ‘Guardian’, and ‘Trustee’. This is not my question. I am confused by the two paragraphs (shown above) that follow the table. Each paragraph is on a different page. I cannot work out if they are both connected in that the second of the
two paragraphs is the subject of the word ‘following’ in the preceding paragraph or if they are unrelated in this regard. Perhaps the word ‘following’ in the first paragraph should be replaced by the word ‘preceding’ in which case it would seem clear that
it is referring to the table above. If this is wrong, then I would seem to understand that the ‘following XML elements’ must be: policyresponse:RuntimePolicy/policyresponse:CodeListExtension policyresponse:ExtensionCanonicalVersionURI policyreponse:ExtensionLocationURI But these doesn’t really make sense either. From: James E Cabral [mailto:jec@mtgmc.com]
Gary, Thank you for the excellent comments and suggestions. I’ve added my responses in red (attached) and uploaded a new Working Draft 7 that includes the changes. __ From: Graham, Gary Attached is a document containing questions and suggestions resulting from an initial look at the main ECF 5 working draft 06 specification document. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]