joshdata / dc-code-prototype Goto Github PK

I'm not going to be that guy, but I will start the ticket. Any XML document eventually wins itself a schema and the attendant standardification.

There's something off in the levels of http://dccode.org/dccode/Title-1/Chapter-10/Subchapter-I/1-1001.08.html

See, e.g., subsection (k)(3)

The form, formc, table, tablec, and PlainText attributes are coming from the data source. Not sure what they mean.

How were these files generated? For any new formats it's always nice to have reference implementations.

What I called placeholders (section-like files for repealed sections) are called tombstones in other jurisdictions, apparently.

I wonder if there's a way to make two containers: (1) law contents; and (2) law annotations. That way, it's easier to traverse the XML. Don't know whether this is a bad idea for other reasons, but it would be nice to be able to just select the contents of the law and not have to worry about children, siblings, etc.

I'm not sure, but it seems like having an XML->seamlesslyinto->HTML format might be problematic for parsing - I wonder if text contents should usually/aways be wrapped in CDATA blocks?

@vzvenyach: Let's add an attribute to title nodes for titles that are positive law?

Gotta fix whatever this was about:

https://github.com/JoshData/dc-code-prototype/blob/02b5489dc9e4a366ce41c15fe087cc06d8ad33df/Division-II/Title-16/Chapter-9/16-916.01.xml

Since links to internal references to other Code sections are generated through (I assume) regular expressions, some sections get left unlinked... see, e.g. 50-1501.02(c)(5)(B)(vii).

http://url.spec.whatwg.org/