30 years after HTML was invented to support accessibility and collaboration for research and academia and the same day the White House released their new accessibility guidance which happens to be the first time they've published formal new policy natively has HTML rather than PDF - https://www.whitehouse.gov/omb/management/ofcio/m-24-08-stre...
This is awesome, thanks for sharing! For those interested here are some similar recent or upcoming efforts to encourage more participatory and generative civic engagement:
Ecological and resource extractive debt is not magic, they have limits and externalities that most financial systems don't fully account for in their balance sheets.
I use PhotoStructure for local management on external hard drives, BackBlaze for offsite backup, and a combination of Flickr and Google Photos for sharing the highlights.
Also note that Data.gov was participating in a Bug Bounty program through HackerOne which means it was actively encouraging people to find vulnerabilities but is no longer able to respond to them - https://hackerone.com/tts
Here's the official statement:
“As data.gov is not a static site, it requires staff monitoring and maintenance to be online,” a GSA spokesperson told FedScoop in a statement. “Because personnel that monitor and maintain the site are currently furloughed, data.gov redirects to usa.gov. The decision to take data.gov offline is consistent with previous funding lapse practices.”
@danso thanks for the feedback on data.gov. I'm part of the small (3 person) team that helps to manage it. If you have a moment to chat I'll see if I can reach out to you to see if you'd be interested in participating in some more in-depth user research in the future. Folks can also always leave feedback via email, github, twitter, and other means - https://www.data.gov/contact
Data.gov and Federal agencies use the same metadata standard (DCAT) that Google Dataset Search is using so much of our metadata is also being syndicated there.
Technology Transformation Service (GSA, U.S. Government) | Web developer (frontend or full stack) | REMOTE or Onsite (DC, San Francisco, NYC, Chicago) | Must be U.S. Citizen or National | Full-Time | $103,672 to $134,776
We're hiring a developer to help support efforts to solicit and analyze public feedback on government service delivery.
This position sits within the Data & Analytics Portfolio (Data.gov, Digital Analytics Program, Feedback Analytics) in the Office of Products and Programs - a sibling of 18F within the Technology Transformation Service at GSA.
For those interested in running for office in your area, https://www.runforoffice.org is a great resource to find open positions and get you started. I'm not affiliated with them, just think they're a great cause.
I know this is an alpha release, but it's invitation only with the invitation being "help us shape the future of our network"
All of which comes across as being much less open and decentralized than the current web.
Even if the technology itself is more distributed than the common standards we're all using now, this sounds more like a walled garden than a truly open network.
There's actually already work being done much like what you describe and it involved the first two rounds of Presidential Innovation Fellows - both to help shape the policy and to facilitate implementation. I'm referring to Project Open Data (http://project-open-data.github.io/) which is backed by an Executive Order to get every major federal agency to catalog all their data assets including those that are not and cannot be public. This full inventory is referred to as the Enterprise Data Inventory (EDI) while the portion of that covering anything that should legally be public is called the Public Data Listing (PDL). Every agency subject to this law is required to post their public listing in a standardized json file at the root of their agency website. The PDL is not only meant to point to datasets that are already publicly available, but it also requires agencies to list datasets that should be public, but have not yet been released or are not yet online. The datasets that are not legally meant to be public must be included in the EDI, but it's up to the discretion of the agency whether they want to list any in their public PDL. Some agencies have been doing that though. Otherwise, the full EDI with an accounting of all non-public datasets will really only be overseen by the White House Office of Manage and Budget and it's up to them to determine what kind of information they'll release about the EDI's they receive from agencies.
As agencies continue to release their Public Data Listings you should be able to find metrics about this at https://www.data.gov/metrics In the future that site should also include metrics like the number of unreleased datasets listed in their PDL data.json file.
Thanks for pointing this out. We've updated the highlighted dataset to something that is better maintained, but if you find other problems please do ticket them on github (https://github.com/GSA/data.gov/issues)
We're also working on some basic automated tests to ensure listings have the correct MIME type (which is incorrect far too often) and that URLs aren't 404s or redirects or HTML pages rather than raw data.