GovTrack.us Wiki - Recent changes [en]

Projects

Govtrack — Wed, 18 Nov 2009 13:59:05 GMT

← Older revision		Revision as of 13:59, 18 November 2009
Line 59:		Line 59:
	* Tell people why they should link to bills on GovTrack: use the status widget, permalink, can link to paragraphs in bill text...		* Tell people why they should link to bills on GovTrack: use the status widget, permalink, can link to paragraphs in bill text...
	* Bill search widget for people to embed on their websites		* Bill search widget for people to embed on their websites
		+	* Using the new GPO FDSYS MODS files for linking to referenced law.
		+	* Using the new GPO FDSYS MODS files to show dates on bill text. To measure how long a bill has been out before a vote.
		+	* Start collecting bill text drafts.

	===Representatives===		===Representatives===

Bill XML

Govtrack — Wed, 18 Nov 2009 13:16:12 GMT

State Codes:

User:Factorial

Govtrack — Wed, 18 Nov 2009 12:51:59 GMT

unblocked Factorial (Talk | contribs)

New page

Bill XML

Govtrack — Wed, 18 Nov 2009 12:49:40 GMT

remove spam

← Older revision		Revision as of 12:49, 18 November 2009
(One intermediate revision not shown)
Line 1:		Line 1:
	Bill XML files contain the full status of each introduced bill in Congress. The information is derived from what is on THOMAS. These files are in data/us/SESSION/bills.		Bill XML files contain the full status of each introduced bill in Congress. The information is derived from what is on THOMAS. These files are in data/us/SESSION/bills.
		+
		+	= Bill Type Codes =

	Each file is named by a bill type prefix followed by the bill's number, and the extension .xml, such as "h123.xml". The bill type prefixes are given below. These are precisely what THOMAS uses.		Each file is named by a bill type prefix followed by the bill's number, and the extension .xml, such as "h123.xml". The bill type prefixes are given below. These are precisely what THOMAS uses.
Line 10:		Line 12:
	* sj: Senate Joint Resolution (i.e. S.J.Res.)		* sj: Senate Joint Resolution (i.e. S.J.Res.)
	* sc: Senate Concurrent Resolution (i.e. S.Con.Res.)		* sc: Senate Concurrent Resolution (i.e. S.Con.Res.)
		+	See [http://www.govtrack.us/blog/2009/11/11/what-are-the-different-types-of-bills/ this blog post] for an explanation of what the different types are.

	Bill numbers, of course, restart in each two-year session.		Bill numbers, of course, restart in each two-year session.
		+
		+	= Bill XML Schema =

	The format of the XML file is:		The format of the XML file is:
Line 21:		Line 26:
	*** '''number''': The number of the bill.		*** '''number''': The number of the bill.
	*** '''updated''': The date the bill XML file was last updated, such as "2007-01-05T15:30:39-05:00".		*** '''updated''': The date the bill XML file was last updated, such as "2007-01-05T15:30:39-05:00".
-	** '''status''' element: Contains a node indicating the current status of the bill. ~~The~~ element ~~inside is one of:~~	+	** '''status''' element: Contains a node indicating the current status of the bill. See below. This element will be deprecated some time in 2010.
-	*** '''~~introduced~~''': ~~The bill has been introduced (and possibly referred~~ to ~~committee), and that's it~~. ~~Has~~ a ~~'''datetime''' attribute giving~~ the ~~date~~ the bill ~~was introduced, such as "2007-01-04".~~	+	** '''state''' element: Currently subject to change. Contains a value indicating the current status of the bill. See below. This element will replace "status" some time in 2010.
-	*** '''calendar''': The bill has passed through committee and has been put on a legislative calendar. ~~Has a '''datetime''' attribute~~.	+
-	*** '''vote''': The bill was voted on in the chamber it was introduced in. Has a '''datetime''' attribute giving the date (and possibly time) of the vote. '''where''' attribute is either "h" or "s". '''result''' attribute is either "pass" or "fail". '''how''' attribute is the method of the vote, such as "voice vote", or "roll" if it was a roll call vote. For a roll call vote, the '''roll''' attribute gives the number of the vote. (Get the year from the date to match this to a vote XML file.) Note that, for instance, simple resolutions end their life span after their first vote, and so this status can indicate a successful life in ~~that case.~~	+
-	*** '''vote2''': The bill was voted on also in the other chamber. Same attributes as '''vote'''.	+
-	*** '''topresident''': The bill passed both chambers and is being presented to the president. Has a '''datetime''' attribute.	+
-	*** '''signed''': The president has signed the bill. Has a '''datetime''' attribute.	+
-	*** '''veto''': The president has vetoed the bill. Has a '''datetime''' attribute.	+
-	*** '''override''': A veto override was attempted. Same attributes as '''vote'''.	+
-	*** '''enacted''': The bill has been enacted. Has a '''datetime''' attribute.	+
	** '''introduced''' element: '''datetime''' attribute gives the date the bill was introduced.		** '''introduced''' element: '''datetime''' attribute gives the date the bill was introduced.
	** '''titles''' element:		** '''titles''' element:
Line 45:		Line 42:
	*** '''calendar''': Bill was put on a legislative calendar or ordered to be reported by a committee.		*** '''calendar''': Bill was put on a legislative calendar or ordered to be reported by a committee.
	*** '''topresident''': Cleared for White House or Presented to President.		*** '''topresident''': Cleared for White House or Presented to President.
-	*** [http://www.superiorpapers.com '''paper writing service''']
	*** '''signed''': Signed by president.		*** '''signed''': Signed by president.
	*** '''veto''': Vetoed by president.		*** '''veto''': Vetoed by president.
Line 51:		Line 47:
	** '''committees''':		** '''committees''':
	*** '''committee''' element: Once per committee or subcommittee assignment. '''name''' attribute gives the name of the main committee. '''subcommittee''' attribute is "" for main committee assignments, otherwise the name of the subcommittee. '''activity''' attribute give some additional information that I do not understand.		*** '''committee''' element: Once per committee or subcommittee assignment. '''name''' attribute gives the name of the main committee. '''subcommittee''' attribute is "" for main committee assignments, otherwise the name of the subcommittee. '''activity''' attribute give some additional information that I do not understand.
		+
		+	= Status Codes =
		+
		+	For the "status" element, there is an element inside with one the following names:
		+
		+	* '''introduced''': The bill has been introduced (and possibly referred to committee), and that's it. Has a '''datetime''' attribute giving the date the bill was introduced, such as "2007-01-04".
		+	* '''calendar''': The bill has passed through committee and has been put on a legislative calendar. Has a '''datetime''' attribute.
		+	* '''vote''': The bill was voted on in the chamber it was introduced in. Has a '''datetime''' attribute giving the date (and possibly time) of the vote. '''where''' attribute is either "h" or "s". '''result''' attribute is either "pass" or "fail". '''how''' attribute is the method of the vote, such as "voice vote", or "roll" if it was a roll call vote. For a roll call vote, the '''roll''' attribute gives the number of the vote. (Get the year from the date to match this to a vote XML file.) Note that, for instance, simple resolutions end their life span after their first vote, and so this status can indicate a successful life in that case.
		+	* '''vote2''': The bill was voted on also in the other chamber. Same attributes as '''vote'''.
		+	* '''topresident''': The bill passed both chambers and is being presented to the president. Has a '''datetime''' attribute.
		+	* '''signed''': The president has signed the bill. Has a '''datetime''' attribute.
		+	* '''veto''': The president has vetoed the bill. Has a '''datetime''' attribute.
		+	* '''override''': A veto override was attempted. Same attributes as '''vote'''.
		+	* '''enacted''': The bill has been enacted. Has a '''datetime''' attribute.
		+
		+	= State Codes =
		+
		+	The newer (and still subject to change) "state" codes are going to replace the current "status" codes some time in 2010. These codes are more precise, and will be created with the expectation that more may be added in the future. They are not ready to be used yet, however.
		+
		+	The codes are:
		+
		+	* INTRODUCED. The bill or resolution was introduced but not yet referred to committee.
		+	* REFERRED. The bill or resolution has been referred to committee in the originating chamber and needs committee action to continue.
		+	* REPORTED. The bill or resolution was reported by committee in the originating chamber and can now continue with floor debate in the originating chamber.
		+	* PASS_OVER:. These are a family of status codes indicating the bill or joint or concurrent resolution has passed favorably in its originating chamber and now goes on to the other chamber. If it failed, the status would be the corresponding FAIL:ORIGINATING:.
		+	** PASS_OVER:HOUSE. The bill or resolution passed the House (Senate next).
		+	** PASS_OVER:SENATE. The bill or resolution passed the Senate (House next).
		+	* PASSED:. These are a family of status codes indicating the bill has passed favorably out of Congress. It is a final status code for resolutions but not for bills. If the vote that PASSED it had gone the other way, the status would be the corresponding FAIL:ORIGINATING: for PASSED:SIMPLERES or FAIL:SECOND: for the others.
		+	** PASSED:SIMPLERES. A simple resolution has been passed in its originating chamber. This is the end of the life for a simple resolution.
		+	** PASSED:CONSTAMEND. A joint resolution which is proposing an amendment to the Constitution has passed both chambers. This is the end of the life for the resolution in the legislative branch. It goes on subsequently to the states.
		+	** PASSED:CONCURRENTRES. A concurrent resolution has been passed by both chambers. This is the end of the life for concurrent resolutions.
		+	** PASSED:BILL. A bill or a joint resolution not proposing an amendment to the constitution has been passed by both chambers. It may require a conference committee first, but will eventually go on to the President.
		+	* PROVKILL:. These are a family of status codes indicating the bill or resolution is provisionally killed, meaning Congress took some action that would often mean the end of life for it (often enough to warrant a status code) but that it could still recover.
		+	** PROVKILL:SUSPENSIONFAILED. The bill or resolution was brought up "under suspension of the rules" and failed that vote. It could be voted on again. If the vote had passed, the status would be one of PASSED, PASS_OVER, etc.
		+	** PROVKILL:CLOTUREFAILED. A cloture vote was taken on the bill or resolution and the vote failed, meaning it was successfully filibustered. If the vote had succeeded, no status would be noted.
		+	** PROVKILL:VETO. The bill "PASSED:BILL" out of Congress but was vetoed by the President. A veto can be overridden. This status applies until an override attempt is made. If the bill was signed instead, the ENACTED status would follow (but not immediately).
		+	* FAIL:. These are a family of status codes indicating the end of life of a bill or resolution. (Unlike PROVKILL, these are always final.)
		+	** FAIL:ORIGINATING:. This is a subgroup for when a bill or resolution fails in its originating chamber.
		+	*** FAIL:ORIGINATING:HOUSE. The bill or resolution failed in its originating chamber, the House.
		+	*** FAIL:ORIGINATING:SENATE. The bill or resolution failed in its originating chamber, the Senate.
		+	** FAIL:SECOND. This is a subgroup for when a bill or joint or concurrent resolution fails in the second chamber. It must have passed in the originating chamber to get this far.
		+	*** FAIL:SECOND:HOUSE. The bill or resolution passed in the Senate but failed in the House.
		+	*** FAIL:SECOND:SENATE. The bill or resolution passed in the House but failed in the Senate.
		+	* OVERRIDE_PASS_OVER:. This is a family of status codes indicating a veto override attempt was successful in the originating chamber, and that it is now up to the second chamber to attempt the override. If the override failed, the status would be one of VETOED:OVERRIDE_FAIL_ORIGINATING:.
		+	** OVERRIDE_PASS_OVER:HOUSE. The House (the originating chamber) succeeded at the veto override. It goes on to the Senate next.
		+	** OVERRIDE_PASS_OVER:SENATE. The Senate (the originating chamber) succeeded at the veto override. It goes on to the House next.
		+	* VETOED:. These are a family of status codes indicating the end of life for a bill that has been vetoed. It is a final status code for a bill.
		+	** VETOED:OVERRIDE_FAIL_ORIGINATING:. This is a subgroup for bills who failed in the veto-override attempt of its originating chamber, which comes first.
		+	*** VETOED:OVERRIDE_FAIL_ORIGINATING:HOUSE. Veto override failed in the House, the bill's originating chamber. It had not gotten to the Senate yet for an override.
		+	*** VETOED:OVERRIDE_FAIL_ORIGINATING:SENATE. Veto override failed in the Senate, the bill's originating chamber. It had not gotten to the House yet for an override.
		+	** VETOED_OVERRIDE_FAIL_SECOND::. This is a subgroup for bills whose veto was successfully overridden in its originating chamber but failed in the veto-override attempt of the other chamber, which comes second. If the override had passed, the status would shortly be ENACTED:VETOOVERRIDE.
		+	*** VETOED_OVERRIDE_FAIL_SECOND:HOUSE. Veto override passed in the Senate (the originating chamber) but failed in the House.
		+	*** VETOED_OVERRIDE_FAIL_SECOND:SENATE. Veto override passed in the House (the originating chamber) but failed in the Senate.
		+	* ENACTED:. These are a family of status codes for bills and joint resolutions not proposing an amendment to the constitution that have been enacted as law. It comes after a short delay between the signature or override and the administrative action to actually make the bill law.
		+	** ENACTED:SIGNED. The president signed the bill.
		+	** ENACTED:VETOOVERRIDE. The bill was vetoed but the veto was overridden in both chambers.

Bill XML

Obvio171 — Tue, 17 Nov 2009 19:12:37 GMT

removed spam

← Older revision		Revision as of 19:12, 17 November 2009
Line 51:		Line 51:
	** '''committees''':		** '''committees''':
	*** '''committee''' element: Once per committee or subcommittee assignment. '''name''' attribute gives the name of the main committee. '''subcommittee''' attribute is "" for main committee assignments, otherwise the name of the subcommittee. '''activity''' attribute give some additional information that I do not understand.		*** '''committee''' element: Once per committee or subcommittee assignment. '''name''' attribute gives the name of the main committee. '''subcommittee''' attribute is "" for main committee assignments, otherwise the name of the subcommittee. '''activity''' attribute give some additional information that I do not understand.
-	~~[http://www.superiorpapers.com paper writing service.com]~~

User:Obvio171

Obvio171 — Tue, 17 Nov 2009 19:11:28 GMT

New user account

New page

← Older revision		Revision as of 13:16, 18 November 2009
Line 65:		Line 65:

	The newer (and still subject to change) "state" codes are going to replace the current "status" codes some time in 2010. These codes are more precise, and will be created with the expectation that more may be added in the future. They are not ready to be used yet, however.		The newer (and still subject to change) "state" codes are going to replace the current "status" codes some time in 2010. These codes are more precise, and will be created with the expectation that more may be added in the future. They are not ready to be used yet, however.
		+
		+	TODO: Bills that go to conference committees, and pass/fail on conference reports.

	The codes are:		The codes are:
Line 79:		Line 81:
	** PASSED:CONCURRENTRES. A concurrent resolution has been passed by both chambers. This is the end of the life for concurrent resolutions.		** PASSED:CONCURRENTRES. A concurrent resolution has been passed by both chambers. This is the end of the life for concurrent resolutions.
	** PASSED:BILL. A bill or a joint resolution not proposing an amendment to the constitution has been passed by both chambers. It may require a conference committee first, but will eventually go on to the President.		** PASSED:BILL. A bill or a joint resolution not proposing an amendment to the constitution has been passed by both chambers. It may require a conference committee first, but will eventually go on to the President.
-	* ~~PROVKILL~~:. These are a family of status codes indicating the bill or resolution is provisionally killed, meaning Congress took some action that would often mean the end of life for it (often enough to warrant a status code) but that it could still recover.	+	* PROV_KILL:. These are a family of status codes indicating the bill or resolution is provisionally killed, meaning Congress took some action that would often mean the end of life for it (often enough to warrant a status code) but that it could still recover.
-	** ~~PROVKILL~~:SUSPENSIONFAILED. The bill or resolution was brought up "under suspension of the rules" and failed that vote. It could be voted on again. If the vote had passed, the status would be one of PASSED, PASS_OVER, etc.	+	** PROV_KILL:SUSPENSIONFAILED. The bill or resolution was brought up "under suspension of the rules" and failed that vote. It could be voted on again. If the vote had passed, the status would be one of PASSED, PASS_OVER, etc.
-	** ~~PROVKILL~~:CLOTUREFAILED. A cloture vote was taken on the bill or resolution and the vote failed, meaning it was successfully filibustered. If the vote had succeeded, no status would be noted.	+	** PROV_KILL:CLOTUREFAILED. A cloture vote was taken on the bill or resolution and the vote failed, meaning it was successfully filibustered. If the vote had succeeded, no status would be noted.
-	** ~~PROVKILL~~:VETO. The bill "PASSED:BILL" out of Congress but was vetoed by the President. A veto can be overridden. This status applies until an override attempt is made. If the bill was signed instead, the ENACTED status would follow (but not immediately).	+	** PROV_KILL:VETO. The bill "PASSED:BILL" out of Congress but was vetoed by the President. A veto can be overridden. This status applies until an override attempt is made. If the bill was signed instead, the ENACTED status would follow (but not immediately).
	* FAIL:. These are a family of status codes indicating the end of life of a bill or resolution. (Unlike PROVKILL, these are always final.)		* FAIL:. These are a family of status codes indicating the end of life of a bill or resolution. (Unlike PROVKILL, these are always final.)
	** FAIL:ORIGINATING:. This is a subgroup for when a bill or resolution fails in its originating chamber.		** FAIL:ORIGINATING:. This is a subgroup for when a bill or resolution fails in its originating chamber.
Line 97:		Line 99:
	*** VETOED:OVERRIDE_FAIL_ORIGINATING:HOUSE. Veto override failed in the House, the bill's originating chamber. It had not gotten to the Senate yet for an override.		*** VETOED:OVERRIDE_FAIL_ORIGINATING:HOUSE. Veto override failed in the House, the bill's originating chamber. It had not gotten to the Senate yet for an override.
	*** VETOED:OVERRIDE_FAIL_ORIGINATING:SENATE. Veto override failed in the Senate, the bill's originating chamber. It had not gotten to the House yet for an override.		*** VETOED:OVERRIDE_FAIL_ORIGINATING:SENATE. Veto override failed in the Senate, the bill's originating chamber. It had not gotten to the House yet for an override.
-	** VETOED_OVERRIDE_FAIL_SECOND::. This is a subgroup for bills whose veto was successfully overridden in its originating chamber but failed in the veto-override attempt of the other chamber, which comes second. If the override had passed, the status would shortly be ENACTED:~~VETOOVERRIDE~~.	+	** VETOED_OVERRIDE_FAIL_SECOND::. This is a subgroup for bills whose veto was successfully overridden in its originating chamber but failed in the veto-override attempt of the other chamber, which comes second. If the override had passed, the status would shortly be ENACTED:VETO_OVERRIDE.
	*** VETOED_OVERRIDE_FAIL_SECOND:HOUSE. Veto override passed in the Senate (the originating chamber) but failed in the House.		*** VETOED_OVERRIDE_FAIL_SECOND:HOUSE. Veto override passed in the Senate (the originating chamber) but failed in the House.
	*** VETOED_OVERRIDE_FAIL_SECOND:SENATE. Veto override passed in the House (the originating chamber) but failed in the Senate.		*** VETOED_OVERRIDE_FAIL_SECOND:SENATE. Veto override passed in the House (the originating chamber) but failed in the Senate.
	* ENACTED:. These are a family of status codes for bills and joint resolutions not proposing an amendment to the constitution that have been enacted as law. It comes after a short delay between the signature or override and the administrative action to actually make the bill law.		* ENACTED:. These are a family of status codes for bills and joint resolutions not proposing an amendment to the constitution that have been enacted as law. It comes after a short delay between the signature or override and the administrative action to actually make the bill law.
	** ENACTED:SIGNED. The president signed the bill.		** ENACTED:SIGNED. The president signed the bill.
-	** ENACTED:~~VETOOVERRIDE~~. The bill was vetoed but the veto was overridden in both chambers.	+	** ENACTED:VETO_OVERRIDE. The bill was vetoed but the veto was overridden in both chambers.