COMPS XML files

[MTwinchek]

When pulling the data from the COMPS section of statutes there is an issue with the appropriations measures where the following coding are not being compiled rather are appearing as continued text.

• <compsdtd:appropriations-para (Item 1) Additionally, where there are tables within the compilation the tables are unformed and show up as small continuous text. (Item 4) Finally, there are coding issues where >. shows up in the code, and when translated shows up on a separate line where it should be inline with the prior text. (Item 3)

Comps utilized for this example: COMPS-1422; COMPS-16716

16716

[bradleechang]

@MTwinchek

The process that creates the USLM versions of COMPS includes a conversion from an older format named "compsdtd". This process currently has limitations. Content that is not yet supported in USLM is passed though in a element that include the original tagging. This preserves the content, but the rendering in the browser will not be styled. This behavior is what you are seeing with , and .

The issue with the period appearing on a separate line is a limitation of the CSS rendering technology. The data is semantically correct in that the period is outside of the quoted content.

We are happy to answer further questions.