U.S. House of Representatives Makes Resolutions in XML
RennieScum writes: "The House of Representatives is turning to technology with their test of XML for use with resolutions according to this article. It reports that the HR has made 100 DTDs and uses Microsoft Word and a special converter to do the job. Testing has begun and their goal is to start using it in January of next year. See also http://xml.house.gov/ And it looks like the DTDs will be free to use and distribute!"
This is the government for you.
When every tool under the sun is using XML schemas, the House is announcing their support for DTDs.
I guess it's still a step forward.
A speech...
Going to http://xml.house.gov/Members/mbr107.xml renders a perfectly viewable directory of representatives in Internet Explorer, but Mozilla dumps it all as raw text in one giant paragraph. What gives?!?
Aw, fuck it. Let's go bowling. - The Big Lebowski
So the government tries to update their use of technology to use an open format like XML and publish the DTD's and inevitably the first 10 slashdot posts complain that the government is too behind the times because that don't use new (and better) XML schemas! Talk about geeks! :)
Who said Freedom was Fair?
It's because of the XSL style sheet they use. You can find it at http://xml.house.gov/Members/member-sorter-vb.xsl.
(Use view source to see the actual XSLT). Notice that they use VBScript!
Who said Freedom was Fair?
From the cited page...
...
Pursuant to Title 17 Section 105 of the United States Code, these DTDs are not subject to copyright protection and are in the public domain.
These DTDs can be redistributed and/or modified freely provided that any derivative works bear some notice that they are derived from it, and any modified versions bear some notice that they have been modified.
Sorry, cupcakes, that's not how the public domain works. If you release it into the public domain, you no longer have *any* control whatsoever upon the modification, reuse, or redistribution of the work. The required notice clause listed above in invalid.
Cite, cite (#3), cite.
Kuroth
<bill status="proposed" name="CBDTPA">
<sponsor name="Fritz Hollings" constituency="Disney">
<violatesAmendment number="1">
<violatesAmendment number="4">
<contribution donor="Disney" amount="24500.00">
<contribution donor="AOL" amount="33000.00">
<contribution donor="National Association of Broadcasters" amount="25000.00">
<excuse>Promote broadband adoption</excuse>
<excuse>Save the arts from extinction</excuse>
</bill>
The article actualy says It shows how each line, name and term has an identifying tag, created by exporting the document from a word processor such as Microsoft Word or Corel WordPerfect into a special XML template.
That would make sense since most of the US government still uses WordPerfect. WordPerfect comes with extensive XML publishing functions including making your own DTDs.
BTW Corel just announced that a new version of Ventura Publisher is coming out in the fall with cross platform XML publishing built in. The next version of WordPerfect is also going to have a much better XML publisher now that they bought XMetaL.
Today's vices may be tomorrow's virtues.
-
http://www.schemavalid.com/faq/xml-schema.html#a4
-
http://www.netcrucible.com/xslt/msxml-faq.htm#Q13
-
http://www.ltg.ed.ac.uk/~ht/XMLData-Reduced.htm
-
http://www.w3.org/TR/1998/NOTE-XML-data/
And thanks to this poster for pointing it out.Who said Freedom was Fair?
And it looks like the DTDs will be free to use and distribute!
Great, now I can make my own crazy laws! Yipee!
DrLunch.com The site that tells you what's for lunch!
I thought the US Government was starting to learn that Microsoft software was to be avoided. By finding more uses for it, I am afraid that it is obviously not true.
Dig the notice at xml.house.gov -- The document type definitions (DTDs) presented on this site were developed at the U.S. House of Representatives by employees of the Federal Government in the course of their official duties. Pursuant to Title 17 Section 105 of the United States Code, these DTDs are not subject to copyright protection and are in the public domain. These DTDs are in draft form. The U.S. House of Representatives assumes no responsibility whatsoever for their use by other parties, and makes no guarantees, expressed or implied, about their quality, reliability, or any other characteristic. These DTDs can be redistributed and/or modified freely provided that any derivative works bear some notice that they are derived from it, and any modified versions bear some notice that they have been modified. (emphasis mine)
...
Either these DTDs are copyrighted and they can place restrictions upon distribution or they arn't. This need people have to control everything is just driving me crazy. The whole reason for Title 17 Section 105 is so that the Government can't put restrictions on this kind of stuff (bills, laws, etc.)
Why use DTDs?
Have you ever tried to use XML Schema? It's a bloated peice of ****. Relax is tons better. And for the government's purposes, DTDs work much better and are an ISO standard.
"And it looks like the DTDs will be free to use and distribute"
Ummmmm if you're using a validating xml parser, you HAVE to have access to the dtd!!! All DTDs have to be free to use!
And the people shall be oppressed, every one by another, and every one by his neighbour Isaiah 3:5
XML is dependent on unicode, as the US Government site's reference states. Follow the W3C to unicode ,
Unicode is required by modern standards such as XML, Java, ECMAScript (JavaScript), LDAP, CORBA 3.0, WML, etc., and is the official way to implement ISO/IEC 10646.
Unicode is owned by Unicode Incorporated and all of it's documents and standarts are issued under a restrictive license with a unilaeral change clause:
Modification by Unicode Unicode shall have the right to modify this Agreement at any time by posting it to this site. The user may not assign any part of this Agreement without Unicodes prior written consent.
Dare I compare this evil arangement to ASCII and other predecesors? To have IBM, M$, Sun and other OWN the very format your data takes and to be able to change it and break previous implimentations at whim, and YOU may not? Who wants to be a plump nickle that any thing vaugly resembling unicode in the future will be called a "derivative" and it's distribution halted? Is this not a collusion of comercial software vendors to control information at it's most basic representation? Does anyone else here see this as the ultimate extention of copyright? Evil, Evil, Evil.
I'd rather see the US government continue to publish in the American Standard for Information Interchange. This extensible standard is no standard at all.
Friends don't help friends install M$ junk.
Congress has always been full of lyahs and chetahs. That it's now full of schemas is really no surpise.
Ergonomica Auctorita Illico!