Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question on strike and insert bill texts #1

Open
iita-atii opened this issue Dec 16, 2024 · 4 comments
Open

Question on strike and insert bill texts #1

iita-atii opened this issue Dec 16, 2024 · 4 comments
Assignees
Labels

Comments

@iita-atii
Copy link

iita-atii commented Dec 16, 2024

How to know which portion of a bill text XML structure is stricken and which portion is the rewrite?

changed does not seem to always accurately reflect this.

amendment-* blocks tend to wrap both portions.

reported-display-style seems the most promising but the rewrite text style is often set at the highest level and not applied to the stricken section by some mechanism i cannot find.

I know it's there as the resulting bills always have the correct text styling applied to each portion but can't find a consistent approach when traversing the XML.

@jonquandt jonquandt transferred this issue from usgpo/api Dec 16, 2024
@jonquandt
Copy link
Member

@iita-atii - moved issue to this repository, since it's related to the Bill XML specifically and not really an API question.

You may want to look at https://xml.house.gov, specifically here https://xml.house.gov/#dtd for some additional information on the bill dtd elements and their values.

For example, https://xml.house.gov/amendment-block.html provides some additional information about the changed element within amendment-block

@jonquandt jonquandt self-assigned this Dec 16, 2024
@iita-atii
Copy link
Author

Nice, sorry didn't realize this was an available repo. I'll take a look around in those docs, much nicer than looking at the raw dtd!

@iita-atii
Copy link
Author

iita-atii commented Dec 18, 2024

hey @jonquandt, is there any place outside of the .xls files the effects of different style attributes (appropriation, defense, OLC, etc) are documented?

Also, the documentation is missing for appropriations-major/intermediate/small did this maybe replace appropriations-para? And some attributes are missing like reported-display-style but not a big deal I realize most efforts are probably being pointed towards USLM work.

@jonquandt
Copy link
Member

jonquandt commented Dec 30, 2024

@iita-atii - after consulting with some colleagues, the web styles documented in the XSLT files are probably your best bet.

You can see what those look like here:
https://www.govinfo.gov/bulkdata/BILLS/resources/billres-details.xsl
https://www.govinfo.gov/bulkdata/BILLS/resources/billres.xsl
https://www.govinfo.gov/bulkdata/BILLS/resources/table.xsl

billres-details.xsl will probably have the most information. For example, on line 3960, there is a directive that applies if reported-display-style and changed are both set:

<xsl:when
     test="(@deleted-display-style = 'strikethrough' or @reported-display-style = 'strikethrough') and @changed = 'deleted'">
	<div class="lbexTextStrikethrough">
	    <xsl:apply-templates/>
	</div>

which calls the following template on line 1390:

.lbexTextStrikethrough
{
    text-decoration:line-through;
}

I do not see appropriations-para in the xsl, but the references to the other versions can be found on line 6368 , which calls the displayHeader template starting on line 6585.

appropriations-[major|intermediate|small are referenced another 40 or so times, generally as an ancestor for the current node styling.

I hope this is helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants