{"id":42,"date":"2015-10-23T13:48:15","date_gmt":"2015-10-23T17:48:15","guid":{"rendered":"http:\/\/blog.law.cornell.edu\/tech\/?p=42"},"modified":"2015-10-23T15:49:07","modified_gmt":"2015-10-23T19:49:07","slug":"a-look-at-indentation","status":"publish","type":"post","link":"https:\/\/blog.law.cornell.edu\/tech\/2015\/10\/23\/a-look-at-indentation\/","title":{"rendered":"A Look at Indentation"},"content":{"rendered":"
Great was the rejoicing in the south tower of Myron Taylor Hall, headquarters of the LII, when we got notice of the bulk release of the Electronic Code of Federal Regulations (eCFR) in XML format.<\/em><\/p>\n What was not to like? The data was as up-to-date as the CFR could get, the XML was much cleaner than the book version, it had a friendly user guide etc., etc., etc..<\/em><\/p>\n It was also different enough from the book XML of the CFR, that we could not simply run it through our existing data enrichment process and serve it to the public as is. So, we curbed our enthusiasm long enough to put together a measured plan to re-do our code.<\/em><\/p>\n We have heard enough from you, our wonderful readers, that text indentation was one of the most valued features of our data presentation. Thus, it was the first feature we chose to implement.<\/em><\/p>\n All this verbosity is the set-up for a look at some of the messy sausage making details of adding indentation to the eCFR.<\/em><\/p>\n If you’re not familiar with XML (eXtensible Markup Language), it’s simply a way of marking up data with a predefined, consistent set of descriptive tags that are both easily human and machine readable. So, when we get XML data from the GPO, it looks something like this…<\/p>\n***<\/code><\/p>\n