W3C home > Mailing lists > Public > public-egov-ig@w3.org > September 2008

Re: Legislation on the web...

From: Anne Washington <AWASHINGTON@crs.loc.gov>
Date: Wed, 10 Sep 2008 13:20:31 -0400
Message-ID: <48C7C99F.EA9C.0041.0@crs.loc.gov>
Cc: "Novak, Kevin" <KevinNovak@aia.org>, public-egov-ig@w3.org, richard.murphy@gsa.gov
To: "Krantz, Peter" <peter.krantz@gmail.com>
Hi everyone,

I recently joined the list-serv and am the author of the handles document quoted below. It was released to the Congressional community but I understand that there is a public release in the works. The intention was to help staffers distribute both internal and external links to bills. A handle is a redirect created for digital preservation (see http://www.handle.net/faq.html). The commercial publishers use DOIs, which are the same technology. The current link structure for legislation has not changed. A handle is an additional access point that provides predictable links over the long-term. Please note that there are handles to THOMAS as well, just remove the dash lis(-lis) at the end.  I coordinated the design and implemented the project if anyone has any questions about it. 

To clarify the origins of congressional information, THOMAS combines three sets of data. First, documents only come from GPO where they finalize and print texts received from Congress (the bill itself, committee reports). Second, the metadata or transaction aspects of legislation (cosponsors, votes, consideration) originate from the databases of the House and Senate. Finally, CRS adds the summaries as mandated by the 1936 statue USC 166(d)(6) in addition to other items.   

Returning to Peter's original question about data and standards, both chambers of Congress (House and Senate) jointly work on a project to draft bills in XML. The House has sponsored the public website http://xml.house.gov at least since 2001, as I recall. The current DTD (this project was started in the days of SGML) and schema are available. There is a whitepaper about how they created the XML drafting system http://xml.house.gov/drafting.htm


From talking to colleagues at state legislatures and national legislatures, it seems we share many similar issues.  I'd be interested in learning more about how W3C standards could be used so legal information can be more easily shared and accessed.


>>> "John Wonderlich" <johnwonderlich@gmail.com> 10:27 AM Wed, 10-Sep 2008 >>>

Hi Kevin,

In case it's helpful, I've appended at the end of this email the document that Daniel Bennett prepared on the "legislative handles" system for permanent bill URLs, which he has sent to the Open House Project google group.  Manually entering the new URLs works for existing legislation, although there aren't yet links to autogenerated stable URLs from THOMAS pages yet.

As far as I know, the current situation with funding for THOMAS upgrades stands with the Legislative Branch Approps subcommittee tentatively approving language in the report for the current years approps directing THOMAS to report back on the feasibility of data level access to legislative information, though this is bogged down in the current approps situation (with Congress expected to pass a Continuing Resolution rather than approps bills).  Here's Rob Pierson from Honda's office discussing the report language:

http://groups.google.com/group/openhouseproject/browse_thread/thread/903b3f1cef0a7c81/c394ec00c157033d?lnk=gst&q=pierson#c394ec00c157033d


And here's the document that Daniel Bennett prepared on "legislative handles":



Legislative Handles 
 (which can be used as Tags/Metadata/Citations)


LIS announces Legislative Handles, a new persistent URL service for creating links to legislative documents. Legislative Handles are a convenient way to cite legislation from either LIS (http://www.congress.gov) or THOMAS (http://thomas.loc.gov). With a simple syntax, Handles make it easy to link to legislation while writing emails or coding web pages. 
Handles are web addresses that do not change over time. The goal of the Handles project is to minimize the impact of any future search engine or database changes by providing persistent predictable links. The current link structure for LIS and THOMAS has not changed. See How to Build Links to Thomas for more information about the current structure. 
How to create a Legislative Handle
To create a Legislative Handle, start with http://hdl.loc.gov/loc.uscongress/ followed by the collection name, legislation. Add a period and the congress number,110. Finally, add a period, the bill abbreviation and the bill number. Add a -lis to link to LIS. Without the suffix, the Handle will resolve to THOMAS.
http://hdl.loc.gov/loc.uscongress/legislation.110hconres196 
http://hdl.loc.gov/loc.uscongress/legislation.110hconres196-lis 
To learn the specifics for building any Handle, see Syntax below. 
How Legislative Handles work
A Handle is a form of uniform resource identifier (URI) that resolves to a uniform resource locator (URL). As a stable pointer, the Handle will not change even if the underlying URL changes over time or the object moves to a new directory. The Global Handle Registry(TM) is run by CNRI (Corporation for National Research Initiatives), making it possible to resolve Handles from any computer on any network. The actual page URL, not the Handle, is shown in the browser address bar when the page is displayed. 
Handles are being introduced in stages and will cover past congresses and additional legislative document types. See Schedule below. Handles are pre-registered, meaning they are created in bulk. The maximum value of the Handle registered is identified on the schedule.
HANDLE SYNTAX
General Syntax - - Legislation (BSS) Syntax 
GENERAL SYNTAX for any Legislative Handle 
Handle Server http://hdl.loc.gov/

Naming Authorityloc.uscongress/
Identifier - Collection legislation.
Identifier - Item 110hconres4544-
Identifier - Suffix lis


http://hdl.loc.gov/loc.uscongress/legislation.110hr4544-lis

The Handle server is the existing proxy server at the Library of Congress.
http://hdl.loc.gov

The naming authority has two parts. The primary naming authority (loc) is managed by the Library of Congress and the secondary naming authority (loc.uscongress) is managed by CRS.
loc.uscongress
The collection identifier is the legislative document or database. In addition to legislation, we anticipate having Handles for the congressional record, nominations and others.
legislation
The item identifier uniquely describes one item in a collection. It contains a series of subparts that logically divide the content within the collection. The unique identifier syntax depends on the collection.
110hconres4544
The suffix indicates whether the Handle will resolve to THOMAS or to LIS. Without a suffix, the Handle will resolve to THOMAS. 
-lis
Handle punctuation
Numbers will *not* use zero padding.
A slash will be used as a delimiter between
- the Handle server and the naming authority hdl.loc.gov/loc.uscongress
- the naming authority and the item identifier loc.uscongress/legislation.110hconres4544
A period will be used as a delimiter between
- subdivisions of the naming authority loc.uscongress
- the collection and the item legislation.110hconres4544
- repeated occurences of a numbers in the item identifier treaty.110.34
A dash will be used as a delimiter before the suffix -lis

LEGISLATION SYNTAX (Bill Summary and Status database)
http:// hdl.loc.gov/loc.uscongress/legislation.###( s | sjres | sconres | sres | hr | hjres | hconres | hres )###-lis
The collection name, legislation, is followed by a period and the Congress number. 
The bill type abbreviation (s | sjres | sconres | sres | hr | hjres | hconres | hres) is followed immediately by the bill number. 
http://hdl.loc.gov/loc.uscongress/legislation.110s254

http://hdl.loc.gov/loc.uscongress/legislation.110sjres10-lis

http://hdl.loc.gov/loc.uscongress/legislation.110sconres33-lis

http://hdl.loc.gov/loc.uscongress/legislation.110sres69-lis 
http://hdl.loc.gov/loc.uscongress/legislation.110hr622

http://hdl.loc.gov/loc.uscongress/legislation.110hjres65-lis

http://hdl.loc.gov/loc.uscongress/legislation.110hconres27-lis

http://hdl.loc.gov/loc.uscongress/legislation.110hres655-lis



On Wed, Sep 10, 2008 at 9:13 AM, Novak, Kevin <KevinNovak@aia.org> wrote:

Peter and All,

Having managed Thomas for four years as one of my many duties at the Library of Congress I wanted to chime in.

Thomas is a very old system and presents many challenges with exposing, managing, and making accessible all of its information. The information and documents coming from the House side of Congress is coming in via XML. The Senate had not yet at the time I left LOC decided on an XML standard for the documents they produce and therefore doesn't offer the accessibility or opportunity for different displays, etc. 

As John may remember (given we had share some information with the Sunlight Foundation and Congressman Honda's office, we had a plan in place to begin major changes to the THOMAS infrastructure, how it communicates and manages data, and how the interface/presentation layer is demonstrated/made available. Of course the challenge was getting the funding to move forward with the plan. 

One item that most are not aware of is that the data in THOMAS originates at the Government Printing Office given how the Senate and House, per policy, are required to document and communicate their activities/bills and the like. All permanent identifiers to the original document reside there. I am surprised to hear that links are changing. Not that I can do anything directly about it now that I am not there anymore but am curious as to what links to documents are not permanent. 

Chris Testa who is the eGov IG subchair for web standards was the direct manager responsible for THOMAS and may be able to provide more insight.

Kevin

Kevin Novak
Vice President, Integrated Web Strategy and Technology
The American Institute of Architects
1735 New York Avenue, NW
Washington, DC 20006

Voice:   202-626-7303
Cell:       202-731-0037
Fax:        202-639-7606
Email:    kevinnovak@aia.org
Website: www.aia.org

AIA NAMED BEST ASSOCIATIONS WEBSITE FOR THE 12th ANNUAL WEBBY AWARDS!
America's Favorite Architecture Tops the Shortlist for International Honor for the Web


The American Institute of Architects is the voice of the architectural profession and the resource for its members in service to society.


From: public-egov-ig-request@w3.org [mailto:public-egov-ig-request@w3.org] On Behalf Of richard.murphy@gsa.gov
Sent: Tuesday, September 09, 2008 9:12 AM
To: johnwonderlich@gmail.com
Cc: Peter Krantz; public-egov-ig@w3.org

Subject: Re: Legislation on the web...

John & All:

I don't think this precisely fits your criteria, but you may be interested in a few OWL-DL ontologies my team maintains. 

1. The US-Privacy Act of 1974 here ...

http://www.osera.gov/privacy.owl


2. The Federal Enterprise Architecture Reference Models

http://www.osera.gov/owl/2004/11/FEA/fea.owl

Best wishes,

Rick

office: 202-501-9199
cell: 202-557-1604

-----public-egov-ig-request@w3..org wrote: -----
To: "Peter Krantz" <peter.krantz@gmail.com>
From: "John Wonderlich" <johnwonderlich@gmail.com>
Sent by: public-egov-ig-request@w3.org
Date: 09/07/2008 01:28PM
cc: public-egov-ig@w3.org
Subject: Re: Legislation on the web...
I recently did a survey of some legislator driven efforts in the US (inserted below).  On a broader level, several sites have grown here to add value to the Library of Congress THOMAS page (the official source of legislation), which has many notable shortfalls, such as links that expire.

GovTrack does the main work of scraping and re-presenting, allowing other sites such as OpenCongress.org to focus on usability and social features.  The source code for both is available.

One chapter of the Open House Project report was about THOMAS upgrades, and is available here.

(blog post below)

                              
Public Legislative Participation
               
August 11th, 2008 by John Wonderlich · 2 Comments
               
                    
The next list I'd like to tackle is legislative participation.

A number of innovative approaches have appeared in various legislative bodies, inviting public participation in what is arguably the most public of all processes: the creation of public policy.  While these projects vary in scope and effect, they all have granted a new level of access and authenticity to public deliberation, recognizing the public as a capable partner in the process of legislating.  

These are all legislative projects operating with official government sponsorship.  While there is a great deal of valuable work done tracking legislation and developing policy outside government, and also pioneering work developing in Congress for communicating with constituents, I'm focusing here on officially sponsored legislative participation.



The Open House Project launched with Speaker Pelosi's endorsement, developing a transparency reform agenda for Congress. 
The Irish House of Parliament, the Oirechtas, held an involved "e-consultation" project on their broadcasting bill.  From their site: 
"The consulters, comprising of members of the Joint Committee of Communications, Marine and Natural Resources and the Office of the Houses of the Oireachtas e-Consultation Working Group, viewed the e-Consultation pilot as a significant departure from previous practice as it involved a dedicated website which allowed for the posting of submissions in a structured manner as well as a discussion forum and it constituted an attempt to communicate directly with the public on legislation and not just target traditional 'stakeholders'." 
Rep. Honda☼ posted legislation and accepted public commentary on their proposed STEM Act. 
Rep. Kuhl☼ launched a "Fix Washington" project, where citizens proposed legislative priorities. 
Senator Lieberman☼ developed the first E-government Act of 2002 in conjunction with a public Web site that collected priorities and suggestions.  From the accompanying report language: 
o    On May 18, 2000, Senators Lieberman and Thompson launched an on-line `experiment in interactive legislation', a website that sought public comments on 44 topics related to possible measures that Congress could take to advance the cause of e-government. Topics were organized into categories, such as `centralized leadership', `funding innovations', and `digital democracy: citizen access and participation,' and ranged from `centralized online portal' to `interoperability standards' to `G-Bay': enhanced online distribution of federal government surplus property.' For each of the topics, a short discussion described the status of current efforts and the `New Idea', or ideas, being offered for consideration. Visitors to the website could then submit their comments on the subject, and read views that had been submitted by others. Nearly 1,000 comments were submitted, approximately one half of which were posted on the website after being reviewed by Committee staff.13
[Footnote] Comments were submitted by private citizens, academicians, federal employees, and even federal agencies. OMB also responded to the website by soliciting views from federal agencies; OMB officials then consolidated agencies' responses and presented them to the Committee as a single document. Opinions, additional information, and alternative proposals submitted over the website proved helpful as Senator Lieberman formulated his electronic government legislation.
[Footnote] 13Comments were reviewed primarily for appropriateness and relevance; Committee staff did not favor any particular viewpoint in deciding which submissions to post. The website was intended to educate the public about the potential of e-government, to solicit input and information on the many topics being considered for possible legislation, and to serve as both an experiment and an example of how the Internet could be used to make government processes more accessible to the public.
Senator Dick Durbin☼ held public discussions on Open Left and Redstate, asking the question: "What Should We Include in our National Broadband Strategy?" 
Politicopia is a public wiki, set up in conjunction with the Utah State Legislature's Rules Committee. 
I'm looking for any other examples.  Others that sort of fit: 


In a sense, the California initiative process involves citizen participation, although it bypasses more than it augments the legislative process. 
The Peer to Patent Project is probably the best designed example of substantive public involvement, although it isn't legislative. 
Any other suggestions? 
                                   
-----Original Message----- 
From: Sheridan, John [mailto:John.Sheridan@nationalarchives.gov.uk] 
Sent: Sun 07/09/2008 19:02 
To: Peter Krantz; public-egov-ig@w3.org 
Cc: jeni@jenitennison.com; Appleby, Paul 
Subject: RE: Legislation on the web...


Peter,

I'm responsible for the development of the UK Government's "official legislation website" - and also for official Gazettes  on the web (the London, Belfast and Edinburgh Gazettes).

See: http://www.opsi.gov.uk/acts/acts2008/ukpga_20080003_en_1 for an example of how we publish legislation (it is semantic HTML and we use a bit of GRDDL too). We've published our XML Schema here: http://www.opsi.gov.uk/legislation/schema/


You might also be interested in "Sem Webbing the London Gazette"
http://2008.xtech.org/public/schedule/detail/528


We're really keen to share ideas!

I've cc'ed some of the others involved.

John Sheridan

Head of e-Services
Office of Public Sector Information
Admiralty Arch
North Side
The Mall
London
SW1A 2WH

Tel: 020 7276 5205
Fax: 020 7276 2661


On Sun, Sep 7, 2008 at 1:19 PM, Peter Krantz <peter.krantz@gmail.com> wrote:

Dear egov-ig group members,

Is there anyone else that is involved in a project that aims to put
your national legislation on the web? We are currently half way
through a project where we use a lot of W3C standards/technology (e.g.
RDFa, OWL, RDFS, XHTML et al) to put swedish legislation online in a
better shape than what exists today.

I was thinking that projects of this type would be similar (from a
technology perspective) in many countries and it would be interesting
to share ideas.

Kind regards,

Peter Krantz--]W5x3Z
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi everyone,
=20
I recently joined the list-serv and am the author of the handles
document quoted below. It was released to the Congressional community
but I understand that there is a public release in the works. The
intention was to help staffers distribute both internal and external
links to bills. A handle is a redirect created for digital preservation
(see http://www.handle.net/faq.html). The commercial publishers use
DOIs, which are the same technology. The current link structure for
legislation has not changed. A handle is an additional access point that
provides predictable links over the long-term. Please note that there
are handles to THOMAS as well, just remove the dash lis(-lis) at the
end.  I coordinated the design and implemented the project if anyone has
any questions about it.=20
=20
To clarify the origins of congressional information, THOMAS combines
three sets of data. First, documents only come from GPO where they
finalize and print texts received from Congress (the bill itself,
committee reports). Second, the metadata or transaction aspects of
legislation (cosponsors, votes, consideration) originate from the
databases of the House and Senate. Finally, CRS adds the summaries as
mandated by the 1936 statue USC 166(d)(6) in addition to other items. =20

=20
Returning to Peter's original question about data and standards, both
chambers of Congress (House and Senate) jointly work on a project to
draft bills in XML. The House has sponsored the public website
http://xml.house.gov ( http://xml.house.gov/ ) at least since 2001,
as I recall. The current DTD (this project was started in the days of
SGML) and schema are available. There is a whitepaper about how they
created the XML drafting system http://xml.house.gov/drafting.htm=20
=20
>From talking to colleagues at state legislatures and national
legislatures, it seems we share many similar issues.  I'd be interested
in learning more about how W3C standards could be used so legal
information can be more easily shared and accessed.
=20

>>> "John Wonderlich" <johnwonderlich@gmail.com> 10:27 AM Wed, 10-Sep
2008 >>>
Hi Kevin,

In case it's helpful, I've appended at the end of this email the
document that Daniel Bennett prepared on the "legislative handles"
system for permanent bill URLs, which he has sent to the Open House
Project google group ( http://groups.google.com/group/openhouseproject
).  Manually entering the new URLs works for existing legislation,
although there aren't yet links to autogenerated stable URLs from THOMAS
pages yet.

As far as I know, the current situation with funding for THOMAS
upgrades stands with the Legislative Branch Approps subcommittee
tentatively approving language in the report for the current years
approps directing THOMAS to report back on the feasibility of data level
access to legislative information, though this is bogged down in the
current approps situation (with Congress expected to pass a Continuing
Resolution rather than approps bills).  Here's Rob Pierson from Honda's
office discussing the report language:

http://groups.google.com/group/openhouseproject/browse_thread/thread/903b3f=
1cef0a7c81/c394ec00c157033d?lnk=3Dgst&q=3Dpierson#c394ec00c157033d


And here's the document that Daniel Bennett prepared on "legislative
handles":

Legislative Handles=20
 (which can be used as Tags/Metadata/Citations)


LIS announces Legislative Handles, a new persistent URL service for
creating links to legislative documents. Legislative Handles are a
convenient way to cite legislation from either LIS
(http://www.congress.gov ( http://www.congress.gov/ )) or THOMAS
(http://thomas.loc.gov ( http://thomas.loc.gov/ )). With a simple
syntax, Handles make it easy to link to legislation while writing emails
or coding web pages.=20
Handles are web addresses that do not change over time. The goal of the
Handles project is to minimize the impact of any future search engine or
database changes by providing persistent predictable links. The current
link structu
re for LIS and THOMAS has not changed. See How to Build
Links to Thomas ( http://www.congress.gov/help/THOMAS_links/links.html )
for more information about the current structure.=20
How to create a Legislative Handle
To create a Legislative Handle, start with
http://hdl.loc.gov/loc.uscongress/ followed by the collection name,
legislation. Add a period and the congress number,110. Finally, add a
period, the bill abbreviation and the bill number. Add a -lis to link to
LIS. Without the suffix, the Handle will resolve to THOMAS.


http://hdl.loc.gov/loc.uscongress/legislation.110hconres196=20
http://hdl.loc.gov/loc.uscongress/legislation.110hconres196-lis=20
To learn the specifics for building any Handle, see Syntax below.=20
How Legislative Handles work
A Handle is a form of uniform resource identifier (URI) that resolves
to a uniform resource locator (URL). As a stable pointer, the Handle
will not change even if the underlying URL changes over time or the
object moves to a new directory. The Global Handle Registry(TM) is run
by CNRI (Corporation for National Research Initiatives), making it
possible to resolve Handles from any computer on any network. The actual
page URL, not the Handle, is shown in the browser address bar when the
page is displayed.=20
Handles are being introduced in stages and will cover past congresses
and additional legislative document types. See Schedule below. Handles
are pre-registered, meaning they are created in bulk. The maximum value
of the Handle registered is identified on the schedule.
HANDLE SYNTAX
General Syntax - - Legislation (BSS) Syntax=20
GENERAL SYNTAX for any Legislative Handle=20
Handle Server=20
http://hdl.loc.gov/=20
Naming Authority
loc.uscongress/
Identifier - Collection=20
legislation.
Identifier - Item=20
110hconres4544-
Identifier - Suffix=20
lis
http://hdl.loc.gov/loc.uscongress/legislation.110hr4544-lis=20
The Handle server is the existing proxy server at the Library of
Congress.
http://hdl.loc.govThe naming authority has two parts. The primary
naming authority (loc) is managed by the Library of Congress and the
secondary naming authority (loc.uscongress) is managed by CRS.
loc.uscongressThe collection identifier is the legislative document or
database. In addition to legislation, we anticipate having Handles for
the congressional record, nominations and others.
legislationThe item identifier uniquely describes one item in a
collection. It contains a series of subparts that logically divide the
content within the collection. The unique identifier syntax depends on
the collection.
110hconres4544The suffix indicates whether the Handle will resolve to
THOMAS or to LIS. Without a suffix, the Handle will resolve to THOMAS.=20
-lis

Handle punctuationNumbers will *not* use zero padding.A slash will be
used as a delimiter between
- the Handle server and the naming authority
hdl.loc.gov/loc.uscongress
- the naming authority and the item identifier
loc.uscongress/legislation.110hconres4544A period will be used as a
delimiter between
- subdivisions of the naming authority loc.uscongress
- the collection and the item legislation.110hconres4544
- repeated occurences of a numbers in the item identifier
treaty.110.34A dash will be used as a delimiter before the suffix -lis

LEGISLATION SYNTAX (Bill Summary and Status database)
http:// hdl.loc.gov/loc.uscongress/legislation.###( s | sjres | sconres
| sres | hr | hjres | hconres | hres )###-lisThe collection name,
legislation, is followed by a period and the Congress number. The bill
type abbreviation (s | sjres | sconres | sres | hr | hjres | hconres |
hres) is followed immediately by the bill number.=20





http://hdl.loc.gov/loc.uscongress/legislation.110s254=20
http://hdl.loc.gov/loc.uscongress/legislation.110sjres10-lis=20
http://hdl.loc.gov/loc.uscongress/legislation.110sconres33-lis=20
http://hdl.loc.gov/loc.uscongress/legislation.110sres69-lis=20
http://hdl.loc.gov/loc.uscongress/legislation.110hr622=20
http://hdl.loc.gov/loc.uscongress/legislation.110hjres65-lis=20
http://hdl.loc.gov/l
oc.uscongress/legislation.110hconres27-lis=20
http://hdl.loc.gov/loc.uscongress/legislation.110hres655-lis=20

On Wed, Sep 10, 2008 at 9:13 AM, Novak, Kevin <KevinNovak@aia.org>
wrote:



Peter and All,
=20
Having managed Thomas for four years as one of my many duties at the
Library of Congress I wanted to chime in.
=20
Thomas is a very old system and presents many challenges with exposing,
managing, and making accessible all of its information. The information
and documents coming from the House side of Congress is coming in via
XML. The Senate had not yet at the time I left LOC decided on an XML
standard for the documents they produce and therefore doesn't offer the
accessibility or opportunity for different displays, etc.=20
=20
As John may remember (given we had share some information with the
Sunlight Foundation and Congressman Honda's office, we had a plan in
place to begin major changes to the THOMAS infrastructure, how it
communicates and manages data, and how the interface/presentation layer
is demonstrated/made available. Of course the challenge was getting the
funding to move forward with the plan.=20
=20
One item that most are not aware of is that the data in THOMAS
originates at the Government Printing Office given how the Senate and
House, per policy, are required to document and communicate their
activities/bills and the like. All permanent identifiers to the original
document reside there. I am surprised to hear that links are changing.
Not that I can do anything directly about it now that I am not there
anymore but am curious as to what links to documents are not permanent.

=20
Chris Testa who is the eGov IG subchair for web standards was the
direct manager responsible for THOMAS and may be able to provide more
insight.
=20
Kevin
=20
Kevin Novak
Vice President, Integrated Web Strategy and Technology
The American Institute of Architects
1735 New York Avenue, NW
Washington, DC 20006
=20
Voice:   202-626-7303
Cell:       202-731-0037
Fax:        202-639-7606
Email:    kevinnovak@aia.org=20
Website:www.aia.org=20
=20

 (
http://outlook.aia.org/exchweb/bin/redir.asp?URL=3Dhttp://www.webbyawards.c=
om/
)
AIA NAMED BEST ASSOCIATIONS WEBSITE FOR THE 12th ANNUAL WEBBY AWARDS!

America's Favorite Architecture (
http://outlook.aia.org/exchweb/bin/redir.asp?URL=3Dhttp://www.favoritearchi=
tecture.org/
) Tops the Shortlist for International Honor for the Web

=20
The American Institute of Architects is the voice of the architectural
profession and the resource for its members in service to society.
=20
=20
From:public-egov-ig-request@w3.org
[mailto:public-egov-ig-request@w3.org] On Behalf Of
richard.murphy@gsa.gov=20
Sent: Tuesday, September 09, 2008 9:12 AM
To: johnwonderlich@gmail.com=20
Cc: Peter Krantz; public-egov-ig@w3.org=20

Subject: Re: Legislation on the web...


=20

John & All:

I don't think this precisely fits your criteria, but you may be
interested in a few OWL-DL ontologies my team maintains.=20

1. The US-Privacy Act of 1974 here ...

http://www.osera.gov/privacy.owl=20

2. The Federal Enterprise Architecture Reference Models

http://www.osera.gov/owl/2004/11/FEA/fea.owl=20

Best wishes,

Rick

office: 202-501-9199
cell: 202-557-1604

=20

-----public-egov-ig-request@w3..org wrote: -----
To: "Peter Krantz" <peter.krantz@gmail.com>
From: "John Wonderlich" <johnwonderlich@gmail.com>
Sent by: public-egov-ig-request@w3.org=20
Date: 09/07/2008 01:28PM
cc: public-egov-ig@w3.org=20
Subject: Re: Legislation on the web...

I recently did a survey of some legislator driven efforts in the US
(inserted below).  On a broader level, several sites have grown here to
add value to the Library of Congress THOMAS ( http://thomas.loc.gov/ )
page (the official source of legislation), which has many notable
shortfalls, such as links that expire.

GovTrack ( http://www.govtrack.us/ ) does the main work of scraping and
re-presenting, allowing other sites such as OpenCongress.org to focus on
usability and social features.  The source code for both is available.

One 
chapter of the Open House Project report was about THOMAS upgrades,
and is available here (
http://www.theopenhouseproject.com/the-open-house-project-report/3-legislat=
ion-database/
).

(blog post (
http://www.theopenhouseproject.com/2008/08/11/public-legislative-participat=
ion/
) below)

                              Public Legislative Participation
               August 11th, 2008 by John Wonderlich =C2=B7 2 Comments
              =20

                   =20
The next list I'd like to tackle is legislative participation.

A number of innovative approaches have appeared in various legislative
bodies, inviting public participation in what is arguably the most
public of all processes: the creation of public policy.  While these
projects vary in scope and effect, they all have granted a new level of
access and authenticity to public deliberation, recognizing the public
as a capable partner in the process of legislating. =20

These are all legislative projects operating with official government
sponsorship.  While there is a great deal of valuable work done tracking
legislation and developing policy outside government, and also
pioneering work developing in Congress for communicating with
constituents, I'm focusing here on officially sponsored legislative
participation.


The Open House Project ( http://www.theopenhouseproject.com/2008/08/ )
launched with Speaker Pelosi's endorsement, developing a transparency
reform agenda for Congress.=20
The Irish House of Parliament, the Oirechtas, held an involved
"e-consultation" project (
http://www.econsultation.ie/ec/econswip.nsf/%28webstartpage%29/5?opendocume=
nt
) on their broadcasting bill.  From their site:=20
"The consulters, comprising of members of the Joint Committee of
Communications, Marine and Natural Resources and the Office of the
Houses of the Oireachtas e-Consultation Working Group, viewed the
e-Consultation pilot as a significant departure from previous practice
as it involved a dedicated website which allowed for the posting of
submissions in a structured manner as well as a discussion forum and it
constituted an attempt to communicate directly with the public on
legislation and not just target traditional 'stakeholders'."=20
Rep. Honda=E2=98=BC posted legislation (
http://honda.house.gov/legislation/2008/stem.shtml ) and accepted
public commentary on their proposed STEM Act.=20
Rep. Kuhl=E2=98=BC launched a "Fix Washington (
http://kuhl.house.gov/blog/index.php/2008/05/16/fix-washington-project/
)" project, where citizens proposed legislative priorities.=20
Senator Lieberman=E2=98=BC developed the first E-government Act (
http://www.whitehouse.gov/omb/egov/g-4-act.html ) of 2002 in
conjunction with a public Web site (
http://web.archive.org/web/20010603050357rn_1/www.senate.gov/%7Egov_affairs=
/egov/
) that collected priorities and suggestions.  From the accompanying
report language:=20

o    On May 18, 2000, Senators Lieberman and Thompson launched an
on-line `experiment in interactive legislation', a website that sought
public comments on 44 topics related to possible measures that Congress
could take to advance the cause of e-government. Topics were organized
into categories, such as `centralized leadership', `funding
innovations', and `digital democracy: citizen access and participation,'
and ranged from `centralized online portal' to `interoperability
standards' to `G-Bay': enhanced online distribution of federal
government surplus property.' For each of the topics, a short discussion
described the status of current efforts and the `New Idea', or ideas,
being offered for consideration. Visitors to the website could then
submit their comments on the subject, and read views that had been
submitted by others. Nearly 1,000 comments were submitted, approximately
one half of which were posted on the website after being reviewed by
Committee staff.13
[Footnote] Comments were submitted by private citizens, academicians,
federal employees, and even federal agencies. OMB also responded to the
website by soliciting views from federal agenci
es; OMB officials then
consolidated agencies' responses and presented them to the Committee as
a single document. Opinions, additional information, and alternative
proposals submitted over the website proved helpful as Senator Lieberman
formulated his electronic government legislation.
[Footnote] 13Comments were reviewed primarily for appropriateness and
relevance; Committee staff did not favor any particular viewpoint in
deciding which submissions to post. The website was intended to educate
the public about the potential of e-government, to solicit input and
information on the many topics being considered for possible
legislation, and to serve as both an experiment and an example of how
the Internet could be used to make government processes more accessible
to the public.
Senator Dick Durbin=E2=98=BC held public discussions on Open Left (
http://www.openleft.com/showDiary.do?diaryId=3D318 ) and Redstate (
http://archive.redstate.com/stories/policy/what_should_we_include_in_our_na=
tional_broadband_strategy
), asking the question: "What Should We Include in our National
Broadband Strategy?"=20
Politicopia is a public wiki, set up in conjunction with the Utah State
Legislature's Rules Committee.=20
I'm looking for any other examples.  Others that sort of fit:=20

In a sense, the California initiative process (
http://www.cainitiative.org/ ) involves citizen participation,
although it bypasses more than it augments the legislative process.=20
The Peer to Patent Project ( http://www.peertopatent.org/ ) is probably
the best designed example of substantive public involvement, although it
isn't legislative.=20
Any other suggestions?=20

                                  =20
-----Original Message-----=20
From: Sheridan, John [mailto:John.Sheridan@nationalarchives.gov.uk]=20
Sent: Sun 07/09/2008 19:02=20
To: Peter Krantz; public-egov-ig@w3.org=20
Cc: jeni@jenitennison.com; Appleby, Paul=20
Subject: RE: Legislation on the web...


Peter,

I'm responsible for the development of the UK Government's "official
legislation website" - and also for official Gazettes  on the web (the
London, Belfast and Edinburgh Gazettes).

See: http://www.opsi.gov.uk/acts/acts2008/ukpga_20080003_en_1 for an
example of how we publish legislation (it is semantic HTML and we use a
bit of GRDDL too). We've published our XML Schema here:
http://www.opsi.gov.uk/legislation/schema/=20

You might also be interested in "Sem Webbing the London Gazette"
http://2008.xtech.org/public/schedule/detail/528=20

We're really keen to share ideas!

I've cc'ed some of the others involved.

John Sheridan

Head of e-Services
Office of Public Sector Information
Admiralty Arch
North Side
The Mall
London
SW1A 2WH

Tel: 020 7276 5205
Fax: 020 7276 2661
=20
=20

On Sun, Sep 7, 2008 at 1:19 PM, Peter Krantz <peter.krantz@gmail.com>
wrote:

Dear egov-ig group members,

Is there anyone else that is involved in a project that aims to put
your national legislation on the web? We are currently half way
through a project where we use a lot of W3C standards/technology (e.g.
RDFa, OWL, RDFS, XHTML et al) to put swedish legislation online in a
better shape than what exists today.

I was thinking that projects of this type would be similar (from a
technology perspective) in many countries and it would be interesting
to share ideas.

Kind regards,

Peter Krantz

=20

=20



--]W5x3Z
Content-Type: multipart/related; boundary="=__Part193094F0.4__="

--=__Part193094F0.4__=
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Description: HTML

<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 6.00.6000.16705" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Hi everyone,</DIV>
<DIV>&nbsp;</DIV>
<DIV>I recently joined the list-serv and am the author of the handles =
document quoted below.&nbsp;It was released to the Congressional community =
but I understand that there is a public release in the works. The =
intention was to help staffers distribute both internal and external links =
to bills. A handle is a redirect created for digital preservation (see <A =
href=3D"http://www.handle.net/faq.html">http://www.handle.net/faq.html</A>)=
.. The commercial publishers use DOIs, which are the same technology. The =
current link structure for legislation has not&nbsp;changed.&nbsp;A handle =
is an additional access point that provides predictable links over the =
long-term. Please note that there are handles to THOMAS as well, just =
remove the dash lis(-lis) at the end.&nbsp;&nbsp;I coordinated the design =
and implemented the project if anyone has any questions about it.&nbsp;</DI=
V>
<DIV>&nbsp;</DIV>
<DIV>To clarify the origins of congressional information, THOMAS combines =
three sets of data. First, documents only come from GPO where they =
finalize and print texts received from Congress (the bill itself, =
committee reports). Second, the metadata or transaction aspects of&nbsp;leg=
islation (cosponsors, votes, consideration) originate from the databases =
of the House and Senate. Finally, CRS adds the summaries as mandated by =
the 1936 statue USC 166(d)(6) in addition to other items.&nbsp;&nbsp; =
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Returning to Peter's original question about data and standards, both =
chambers of Congress (House and Senate) jointly work on&nbsp;a project to =
draft bills in XML. The House has sponsored the public website <A =
href=3D"http://xml.house.gov/">http://xml.house.gov</A>&nbsp;at least =
since 2001, as I recall. The current DTD (this project was started in the =
days of SGML) and schema&nbsp;are available.&nbsp;There is a whitepaper =
about how they created the XML drafting system <A href=3D"http://xml.house.=
gov/drafting.htm">http://xml.house.gov/drafting.htm</A></DIV>
<DIV>&nbsp;</DIV>
<DIV>From talking to colleagues at state legislatures and national =
legislatures, it seems we share many similar issues.&nbsp; I'd be =
interested in learning more about how W3C standards could be used so legal =
information can be more easily shared and accessed.</DIV>
<DIV>&nbsp;</DIV>
<DIV><BR>&gt;&gt;&gt; "John Wonderlich" &lt;johnwonderlich@gmail.com&gt; =
10:27 AM Wed, 10-Sep 2008 &gt;&gt;&gt;<BR></DIV>
<DIV dir=3Dltr>Hi Kevin,<BR><BR>In case it's helpful, I've appended at the =
end of this email the document that Daniel Bennett prepared on the =
"legislative handles" system for permanent bill URLs, which he has sent to =
the Open House Project <A href=3D"http://groups.google.com/group/openhousep=
roject">google group</A>.&nbsp; Manually entering the new URLs works for =
existing legislation, although there aren't yet links to autogenerated =
stable URLs from THOMAS pages yet.<BR><BR>As far as I know, the current =
situation with funding for THOMAS upgrades stands with the Legislative =
Branch Approps subcommittee tentatively approving language in the report =
for the current years approps directing THOMAS to report back on the =
feasibility of data level access to legislative information, though this =
is bogged down in the current approps situation (with Congress expected to =
pass a Continuing Resolution rather than approps bills).&nbsp; Here's Rob =
Pierson from Honda's office discussing the report language:<BR><BR><A =
href=3D"http://groups.google.com/group/openhouseproject/browse_thread/threa=
d/903b3f1cef0a7c81/c394ec00c157033d?lnk=3Dgst&amp;q=3Dpierson#c394ec00c1570=
33d">http://groups.google.com/group/openhouseproject/browse_thread/thread/9=
03b3f1cef0a7c81/c394ec00c157033d?lnk=3Dgst&amp;q=3Dpierson#c394ec00c157033d=
</A><BR><BR>And here's the document that Daniel Bennett prepared on =
"legislative handles":<BR><BR>
<DIV style=3D"MARGIN-LEFT: 40px">
<DIV id=3Dgearsstatus style=3D"TEXT-ALIGN: right"><IMG id=3Dgears-status =
src=3D"cid:CFTNEVTKFLFS.gears_online.gif"></DIV>Legislative Handles <BR =
id=3Df3j30>&nbsp;(which can be used as Tags/Metadata/Citations)<BR =
id=3Df3j31><BR id=3Df3j32>
<P id=3Df3j33>LIS announces Legislative Handles, a new persistent URL =
service for creating links to legislative documents. Legislative Handles =
are a convenient way to cite legislation from either LIS (<A id=3Df3j34 =
href=3D"http://www.congress.gov/">http://www.congress.gov</A>) or THOMAS =
(<A id=3Df3j35 href=3D"http://thomas.loc.gov/">http://thomas.loc.gov</A>). =
With a simple syntax, Handles make it easy to link to legislation while =
writing emails or coding web pages. </P>
<P id=3Df3j36>Handles are web addresses that do not change over time. The =
goal of the Handles project is to minimize the impact of any future search =
engine or database changes by providing persistent predictable links. The =
current link structure for LIS and THOMAS has not changed. See <A =
id=3Df3j37 href=3D"http://www.congress.gov/help/THOMAS_links/links.html">Ho=
w to Build Links to Thomas</A> for more information about the current =
structure. </P>
<P id=3Df3j38><B id=3Df3j39>How to create a Legislative Handle</B></P>
<P id=3Df3j310>To create a Legislative Handle, start with <A href=3D"http:/=
/hdl.loc.gov/loc.uscongress/">http://hdl.loc.gov/loc.uscongress/</A> =
followed by the collection name, legislation. Add a period and the =
congress number,110. Finally, add a period, the bill abbreviation and the =
bill number. Add a -lis to link to LIS. Without the suffix, the Handle =
will resolve to THOMAS.</P>
<BLOCKQUOTE id=3Df3j311>
<P id=3Df3j312><A id=3Df3j313 href=3D"http://hdl.loc.gov/loc.uscongress/leg=
islation.110hconres196">http://hdl.loc.gov/loc.uscongress/legislation.110hc=
onres196</A> <BR id=3Df3j314><A id=3Df3j315 href=3D"http://hdl.loc.gov/loc.=
uscongress/legislation.110hconres196-lis">http://hdl.loc.gov/loc.uscongress=
/legislation.110hconres196-lis </A></P></BLOCKQUOTE>
<P id=3Df3j316>To learn the specifics for building any Handle, see <A =
id=3Df3j317>Syntax</A> below. </P>
<P id=3Df3j318><B id=3Df3j319>How Legislative Handles work</B></P>
<P id=3Df3j320>A Handle is a form of uniform resource identifier (URI) =
that resolves to a uniform resource locator (URL). As a stable pointer, =
the Handle will not change even if the underlying URL changes over time or =
the object moves to a new directory. The Global Handle Registry(TM) is run =
by CNRI (Corporation for National Research Initiatives), making it =
possible to resolve Handles from any computer on any network. The actual =
page URL, not the Handle, is shown in the browser address bar when the =
page is displayed. </P>
<P id=3Df3j321>Handles are being introduced in stages and will cover past =
congresses and additional legislative document types. See <A id=3Df3j322>Sc=
hedule</A> below. Handles are pre-registered, meaning they are created in =
bulk. The maximum value of the Handle registered is identified on the =
schedule.</P>
<P id=3Df3j323><A id=3Df3j324 name=3Dsyntax></A><B id=3Df3j325>HANDLE =
SYNTAX</B></P>
<P id=3Df3j326><A id=3Df3j327>General Syntax</A> - - <A id=3Df3j328>Legisla=
tion (BSS) Syntax</A> </P>
<P id=3Df3j329><A id=3Dgeneral name=3Dgeneral></A><B id=3Df3j330>GENERAL =
SYNTAX for any Legislative Handle </B></P>
<TABLE id=3Df3j331 width=3D412 border=3D1>
<TBODY id=3Df3j332>
<TR id=3Df3j333>
<TH id=3Df3j334 scope=3Drow width=3D199>
<DIV id=3Df3j335 align=3Dleft>Handle Server </DIV></TH>
<TD id=3Df3j336 width=3D130><A href=3D"http://hdl.loc.gov">http://hdl.loc.g=
ov</A></TD>
<TD id=3Df3j337 width=3D61>
<DIV id=3Df3j338 align=3Dcenter>/</DIV></TD></TR>
<TR id=3Df3j339>
<TH id=3Df3j340 scope=3Drow>
<DIV id=3Df3j341 align=3Dleft>Naming Authority</DIV></TH>
<TD id=3Df3j342>loc.uscongress</TD>
<TD id=3Df3j343>
<DIV id=3Df3j344 align=3Dcenter>/</DIV></TD></TR>
<TR id=3Df3j345>
<TH id=3Df3j346 scope=3Drow>
<DIV id=3Df3j347 align=3Dleft>Identifier - Collection </DIV></TH>
<TD id=3Df3j348>legislation</TD>
<TD id=3Df3j349>
<DIV id=3Df3j350 align=3Dcenter>.</DIV></TD></TR>
<TR id=3Df3j351>
<TH id=3Df3j352 scope=3Drow>
<DIV id=3Df3j353 align=3Dleft>Identifier - Item </DIV></TH>
<TD id=3Df3j354>110hconres4544</TD>
<TD id=3Df3j355>
<DIV id=3Df3j356 align=3Dcenter>-</DIV></TD></TR>
<TR id=3Df3j357>
<TH id=3Df3j358 scope=3Drow>
<DIV id=3Df3j359 align=3Dleft>Identifier - Suffix </DIV></TH>
<TD id=3Df3j360>lis</TD>
<TD id=3Df3j361><BR id=3Df3j362></TD></TR></TBODY></TABLE>
<DIV id=3Df3j363 align=3Dleft><A id=3Df3j364 href=3D"http://hdl.loc.gov/loc=
..uscongress/legislation.110hr4544-lis">http://hdl.loc.gov/loc.uscongress/le=
gislation.110hr4544-lis</A></DIV>
<OL id=3Df3j365>
<LI id=3Df3j366>The Handle server is the existing proxy server at the =
Library of Congress.<BR id=3Df3j367><A href=3D"http://hdl.loc.gov">http://h=
dl.loc.gov</A>
<LI id=3Df3j368>The naming authority has two parts. The primary naming =
authority (loc) is managed by the Library of Congress and the secondary =
naming authority (loc.uscongress) is managed by CRS.<BR id=3Df3j369>loc.usc=
ongress
<LI id=3Df3j370>The collection identifier is the legislative document or =
database. In addition to legislation, we anticipate having Handles for the =
congressional record, nominations and others.<BR id=3Df3j371>legislation
<LI id=3Df3j372>The item identifier uniquely describes one item in a =
collection. It contains a series of subparts that logically divide the =
content within the collection. The unique identifier syntax depends on the =
collection.<BR id=3Df3j373>110hconres4544
<LI id=3Df3j374>The suffix indicates whether the Handle will resolve to =
THOMAS or to LIS. Without a suffix, the Handle will resolve to THOMAS. <BR =
id=3Df3j375>-lis</LI></OL>
<P id=3Df3j376><B id=3Df3j377>Handle punctuation</B></P>
<UL id=3Df3j378>
<LI id=3Df3j379>Numbers will *not* use zero padding.
<LI id=3Df3j380>A slash will be used as a delimiter between<BR id=3Df3j381>=
- the Handle server and the naming authority <I id=3Df3j382><A href=3D"http=
://hdl.loc.gov/loc.uscongress">hdl.loc.gov/loc.uscongress</A></I><BR =
id=3Df3j383>- the naming authority and the item identifier <I id=3Df3j384>l=
oc.uscongress/legislation.110hconres4544</I>
<LI id=3Df3j385>A period will be used as a delimiter between<BR id=3Df3j386=
>- subdivisions of the naming authority <I id=3Df3j387>loc.uscongress</I><B=
R id=3Df3j388>- the collection and the item <I id=3Df3j389>legislation.110h=
conres4544</I><BR id=3Df3j390>- repeated occurences of a numbers in the =
item identifier <I id=3Df3j391>treaty.110.34</I>
<LI id=3Df3j392>A dash will be used as a delimiter before the suffix <I =
id=3Df3j393>-lis</I><BR id=3Df3j394></LI></UL>
<P id=3Df3j395><A id=3Dlegislation name=3Dlegislation></A><B id=3Df3j396>LE=
GISLATION SYNTAX (Bill Summary and Status database)</B><BR id=3Df3j397>http=
:// <A href=3D"http://hdl.loc.gov/loc.uscongress/legislation.###(">hdl.loc.=
gov/loc.uscongress/legislation.###(</A> s | sjres | sconres | sres | hr | =
hjres | hconres | hres )###-lis</P>
<UL id=3Df3j398>
<LI id=3Df3j399>The collection name, legislation, is followed by a period =
and the Congress number.=20
<LI id=3Df3j3100>The bill type abbreviation (s | sjres | sconres | sres | =
hr | hjres | hconres | hres) is followed immediately by the bill number. =
</LI></UL>
<BLOCKQUOTE id=3Df3j3101>
<BLOCKQUOTE id=3Df3j3102>
<P id=3Df3j3103><A id=3Df3j3104 href=3D"http://hdl.loc.gov/loc.uscongress/l=
egislation.110s254">http://hdl.loc.gov/loc.uscongress/legislation.110s254</=
A><BR id=3Df3j3105><A id=3Df3j3106 href=3D"http://hdl.loc.gov/loc.uscongres=
s/legislation.110sjres10-lis">http://hdl.loc.gov/loc.uscongress/legislation=
..110sjres10-lis</A><BR id=3Df3j3107><A id=3Df3j3108 href=3D"http://hdl.loc.=
gov/loc.uscongress/legislation.110sconres33-lis">http://hdl.loc.gov/loc.usc=
ongress/legislation.110sconres33-lis</A><BR id=3Df3j3109><A id=3Df3j3110 =
href=3D"http://hdl.loc.gov/loc.uscongress/legislation.110sres69-lis">http:/=
/hdl.loc.gov/loc.uscongress/legislation.110sres69-lis </A></P>
<P id=3Df3j3111><A id=3Df3j3112 href=3D"http://hdl.loc.gov/loc.uscongress/l=
egislation.110hr622">http://hdl.loc.gov/loc.uscongress/legislation.110hr622=
</A><BR id=3Df3j3113><A id=3Df3j3114 href=3D"http://hdl.loc.gov/loc.uscongr=
ess/legislation.110hjres65-lis">http://hdl.loc.gov/loc.uscongress/legislati=
on.110hjres65-lis</A><BR id=3Df3j3115><A id=3Df3j3116 href=3D"http://hdl.lo=
c.gov/loc.uscongress/legislation.110hconres27-lis">http://hdl.loc.gov/loc.u=
scongress/legislation.110hconres27-lis</A><BR id=3Df3j3117><A id=3Df3j3118 =
href=3D"http://hdl.loc.gov/loc.uscongress/legislation.110hres655-lis">http:=
//hdl.loc.gov/loc.uscongress/legislation.110hres655-lis</A></P></BLOCKQUOTE=
></BLOCKQUOTE></DIV><BR>
<DIV class=3Dgmail_quote>On Wed, Sep 10, 2008 at 9:13 AM, Novak, Kevin =
<SPAN dir=3Dltr>&lt;<A href=3D"mailto:KevinNovak@aia.org">KevinNovak@aia.or=
g</A>&gt;</SPAN> wrote:<BR>
<BLOCKQUOTE class=3Dgmail_quote style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt =
0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV lang=3DEN-US vlink=3D"purple" link=3D"blue">
<DIV>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">Peter and =
All,</SPAN></P>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></SPAN>&nbsp;</P>=

<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">Having managed =
Thomas for four years as one of my many duties at the Library of Congress =
I wanted to chime in.</SPAN></P>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></SPAN>&nbsp;</P>=

<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">Thomas is a very =
old system and presents many challenges with exposing, managing, and =
making accessible all of its information. The information and documents =
coming from the House side of Congress is coming in via XML. The Senate =
had not yet at the time I left LOC decided on an XML standard for the =
documents they produce and therefore doesn't offer the accessibility or =
opportunity for different displays, etc. </SPAN></P>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></SPAN>&nbsp;</P>=

<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">As John may =
remember (given we had share some information with the Sunlight Foundation =
and Congressman Honda's office, we had a plan in place to begin major =
changes to the THOMAS infrastructure, how it communicates and manages =
data, and how the interface/presentation layer is demonstrated/made =
available. Of course the challenge was getting the funding to move forward =
with the plan. </SPAN></P>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></SPAN>&nbsp;</P>=

<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">One item that =
most are not aware of is that the data in THOMAS originates at the =
Government Printing Office given how the Senate and House, per policy, are =
required to document and communicate their activities/bills and the like. =
All permanent identifiers to the original document reside there. I am =
surprised to hear that links are changing. Not that I can do anything =
directly about it now that I am not there anymore but am curious as to =
what links to documents are not permanent. </SPAN></P>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></SPAN>&nbsp;</P>=

<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">Chris Testa who =
is the eGov IG subchair for web standards was the direct manager responsibl=
e for THOMAS and may be able to provide more insight.</SPAN></P>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></SPAN>&nbsp;</P>=

<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">Kevin</SPAN></P>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></SPAN>&nbsp;</P>=

<P><B><SPAN style=3D"COLOR: rgb(31,73,125)">Kevin Novak</SPAN></B></P>
<P><I><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">Vice =
President, Integrated Web Strategy and Technology</SPAN></I></P>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">The American =
Institute of Architects</SPAN></P>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">1735 New York =
Avenue, NW</SPAN></P>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">Washington, DC =
20006</SPAN></P>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></SPAN>&nbsp;</P>=

<P><B><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">Voice:</SPAN><=
/B><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">&nbsp;&nbsp; =
202-626-7303</SPAN></P>
<P><B><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">Cell:</SPAN></=
B><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; 202-731-0037</SPAN></P>
<P><B><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">Fax:</SPAN></B=
><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; 202-639-7606</SPAN></P>
<P><B><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">Email:</SPAN><=
/B><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">&nbsp;&nbsp;&nbsp=
; <A href=3D"mailto:kevinnovak@aia.org" target=3D_blank>kevinnovak@aia.org<=
/A></SPAN></P>
<P><B><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">Website:</SPAN=
></B><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"> <A href=3D"htt=
p://www.aia.org" target=3D_blank>www.aia.org</A></SPAN></P>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></SPAN>&nbsp;</P>=

<TABLE style=3D"WIDTH: 5.25in; BORDER-COLLAPSE: collapse" cellSpacing=3D0 =
cellPadding=3D0 width=3D504 border=3D0>
<TBODY>
<TR style=3D"HEIGHT: 14.25pt">
<TD style=3D"PADDING-RIGHT: 5.4pt; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: =
0in; WIDTH: 0.65in; PADDING-TOP: 0in; HEIGHT: 14.25pt" vAlign=3Dtop =
width=3D62 rowSpan=3D2>
<P><A href=3D"http://outlook.aia.org/exchweb/bin/redir.asp?URL=3Dhttp://www=
..webbyawards.com/" target=3D_blank><SPAN style=3D"FONT-SIZE: 11pt; COLOR: =
rgb(31,73,125); TEXT-DECORATION: none"><IMG height=3D38 alt=3Dhttp://outloo=
k.aia.org/exchange/knovak/Inbox/sharepoint access-2.EML/1_multipart/image00=
1.jpg?Security=3D2 src=3D"cid:NGXRZVKRBPHJ.IMAGE.jpeg" width=3D48 =
border=3D0></SPAN></A><SPAN style=3D"COLOR: rgb(31,73,125)"></SPAN></P></TD=
>
<TD style=3D"PADDING-RIGHT: 5.4pt; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: =
0in; WIDTH: 4.6in; PADDING-TOP: 0in; HEIGHT: 14.25pt" vAlign=3Dtop =
width=3D442>
<P><SPAN style=3D"FONT-SIZE: 8pt; COLOR: rgb(31,73,125)">AIA NAMED BEST <A =
name=3D11c4c65376d992e3_webby_entry_associations>ASSOCIATION</A>S WEBSITE =
FOR THE 12th ANNUAL WEBBY AWARDS!</SPAN><SPAN style=3D"COLOR: rgb(31,73,125=
)"></SPAN></P></TD></TR>
<TR style=3D"HEIGHT: 11.65pt">
<TD style=3D"PADDING-RIGHT: 5.4pt; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: =
0in; WIDTH: 4.6in; PADDING-TOP: 0in; HEIGHT: 11.65pt" vAlign=3Dtop =
width=3D442>
<P><SPAN style=3D"FONT-SIZE: 8pt; COLOR: rgb(31,73,125)"><A href=3D"http://=
outlook.aia.org/exchweb/bin/redir.asp?URL=3Dhttp://www.favoritearchitecture=
..org/" target=3D_blank>America's Favorite Architecture</A> Tops the =
Shortlist for International Honor for the Web</SPAN><SPAN style=3D"COLOR: =
rgb(31,73,125)"></SPAN></P></TD></TR></TBODY></TABLE>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></SPAN>&nbsp;</P>=

<P><B><I><SPAN style=3D"FONT-SIZE: 10pt; COLOR: rgb(31,73,125)">The =
American Institute&nbsp;of Architects is <U>the</U> voice of&nbsp;the =
architectural profession and <U>the </U>resource&nbsp;for its members in =
service to society.</SPAN></I></B><SPAN style=3D"FONT-SIZE: 11pt; COLOR: =
rgb(31,73,125)"></SPAN></P>
<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></SPAN>&nbsp;</P>=

<P><SPAN style=3D"FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></SPAN>&nbsp;</P>=

<DIV style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
rgb(181,196,223) 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; =
BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P><B><SPAN style=3D"FONT-SIZE: 10pt">From:</SPAN></B><SPAN style=3D"FONT-S=
IZE: 10pt"> <A href=3D"mailto:public-egov-ig-request@w3.org" target=3D_blan=
k>public-egov-ig-request@w3.org</A> [mailto:<A href=3D"mailto:public-egov-i=
g-request@w3.org" target=3D_blank>public-egov-ig-request@w3.org</A>] <B>On =
Behalf Of </B><A href=3D"mailto:richard.murphy@gsa.gov" target=3D_blank>ric=
hard.murphy@gsa.gov</A><BR><B>Sent:</B> Tuesday, September 09, 2008 9:12 =
AM<BR><B>To:</B> <A href=3D"mailto:johnwonderlich@gmail.com" target=3D_blan=
k>johnwonderlich@gmail.com</A><BR><B>Cc:</B> Peter Krantz; <A href=3D"mailt=
o:public-egov-ig@w3.org" target=3D_blank>public-egov-ig@w3.org</A>
<DIV>
<DIV></DIV>
<DIV class=3DWj3C7c><BR><B>Subject:</B> Re: Legislation on the web...</DIV>=
</DIV></SPAN>
<P></P></DIV>
<P>&nbsp;</P>
<DIV>
<DIV>
<DIV></DIV>
<DIV class=3DWj3C7c>
<P style=3D"MARGIN-BOTTOM: 12pt">John &amp; All:<BR><BR>I don't think this =
precisely fits your criteria, but you may be interested in a few OWL-DL =
ontologies my team maintains. <BR><BR>1. The US-Privacy Act of 1974 here =
....<BR><BR><A href=3D"http://www.osera.gov/privacy.owl" target=3D_blank>htt=
p://www.osera.gov/privacy.owl</A><BR><BR>2. The Federal Enterprise =
Architecture Reference Models<BR><BR><A href=3D"http://www.osera.gov/owl/20=
04/11/FEA/fea.owl" target=3D_blank>http://www.osera.gov/owl/2004/11/FEA/fea=
..owl</A></P></DIV></DIV>
<DIV>
<DIV>
<DIV></DIV>
<DIV class=3DWj3C7c>
<P>Best&nbsp;wishes,<BR><BR>Rick<BR><BR>office:&nbsp;202-501-9199<BR>cell:&=
nbsp;202-557-1604</P>
<DIV>
<P>&nbsp;</P></DIV>
<P style=3D"MARGIN-BOTTOM: 12pt"><SPAN style=3D"COLOR: rgb(153,0,153)">----=
-public-egov-ig-request@w3..org wrote: -----</SPAN></P>
<P style=3D"MARGIN-BOTTOM: 12pt">To: "Peter Krantz" &lt;<A href=3D"mailto:p=
eter.krantz@gmail.com" target=3D_blank>peter.krantz@gmail.com</A>&gt;<BR>Fr=
om: "John Wonderlich" &lt;<A href=3D"mailto:johnwonderlich@gmail.com" =
target=3D_blank>johnwonderlich@gmail.com</A>&gt;<BR>Sent by: <A href=3D"mai=
lto:public-egov-ig-request@w3.org" target=3D_blank>public-egov-ig-request@w=
3.org</A><BR>Date: 09/07/2008 01:28PM<BR>cc: <A href=3D"mailto:public-egov-=
ig@w3.org" target=3D_blank>public-egov-ig@w3.org</A><BR>Subject: Re: =
Legislation on the web...</P></DIV></DIV>
<DIV>
<DIV>
<DIV></DIV>
<DIV class=3DWj3C7c>
<P>I recently did a survey of some legislator driven efforts in the US =
(inserted below).&nbsp; On a broader level, several sites have grown here =
to add value to the Library of Congress <A href=3D"http://thomas.loc.gov/" =
target=3D_blank>THOMAS</A> page (the official source of legislation), =
which has many notable shortfalls, such as links that expire.<BR><BR><A =
href=3D"http://www.govtrack.us/" target=3D_blank>GovTrack</A> does the =
main work of scraping and re-presenting, allowing other sites such as <A =
href=3D"http://OpenCongress.org" target=3D_blank>OpenCongress.org</A> to =
focus on usability and social features.&nbsp; The source code for both is =
available.<BR><BR>One chapter of the Open House Project report was about =
THOMAS upgrades, and is available <A href=3D"http://www.theopenhouseproject=
..com/the-open-house-project-report/3-legislation-database/" target=3D_blank=
>here</A>.<BR><BR>(<A href=3D"http://www.theopenhouseproject.com/2008/08/11=
/public-legislative-participation/" target=3D_blank>blog post</A> =
below)<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp=
;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp=
;&nbsp;&nbsp; </P>
<H2>Public Legislative Participation</H2>
<P>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbs=
p; </P>
<H4>August 11th, 2008 by John Wonderlich =C2=B7 2 Comments</H4>
<P>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbs=
p; </P></DIV></DIV>
<DIV>
<DIV>
<DIV></DIV>
<DIV class=3DWj3C7c>
<P>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbs=
p; &nbsp;&nbsp;&nbsp;&nbsp; </P>
<P><SPAN>The next list I'd like to tackle is </SPAN><B>legislative =
participation</B><SPAN>.</SPAN><BR><BR><SPAN>A number of innovative =
approaches have appeared in various legislative bodies, inviting public =
participation in what is arguably the most public of all processes: the =
creation of public policy.&nbsp; While these projects vary in scope and =
effect, they all have granted a new level of access and authenticity to =
public deliberation, recognizing the public as a capable partner in the =
process of legislating.&nbsp; </SPAN><BR><BR><SPAN>These are all legislativ=
e projects operating with official government sponsorship.&nbsp; While =
there is a great deal of valuable work done tracking legislation and =
developing policy outside government, and also pioneering work developing =
in Congress for communicating with constituents, I'm focusing here on =
officially sponsored legislative participation.</SPAN><BR><BR><BR></P>
<UL type=3Ddisc>
<LI><SPAN>The <A title=3D"Open House Project" href=3D"http://www.theopenhou=
seproject.com/2008/08/" target=3D_blank>Open House Project</A> launched =
with Speaker Pelosi's endorsement, developing a transparency reform agenda =
for Congress.</SPAN>=20
<LI><SPAN>The Irish House of Parliament, the Oirechtas, held an involved =
"e-consultation" <A title=3Dproject href=3D"http://www.econsultation.ie/ec/=
econswip.nsf/(webstartpage)/5?opendocument" target=3D_blank>project</A> on =
their broadcasting bill.&nbsp; From their site: </SPAN></LI></UL>
<UL type=3Ddisc>
<UL type=3Dcircle>
<LI>"The consulters, comprising of members of the Joint Committee of =
Communications, Marine and Natural Resources and the Office of the Houses =
of the Oireachtas e-Consultation Working Group, viewed the e-Consultation =
pilot as a significant departure from previous practice as it involved a =
dedicated website which allowed for the posting of submissions in a =
structured manner as well as a discussion forum and it constituted an =
attempt to communicate directly with the public on legislation and not =
just target traditional 'stakeholders'." </LI></UL></UL>
<UL type=3Ddisc>
<LI>Rep. Honda<SPAN>=E2=98=BC</SPAN> <A title=3D"posted legislation" =
href=3D"http://honda.house.gov/legislation/2008/stem.shtml" target=3D_blank=
>posted legislation</A> and accepted public commentary on their proposed =
STEM Act.=20
<LI>Rep. Kuhl<SPAN>=E2=98=BC</SPAN> launched a "<A title=3D"Fix Washington"=
 href=3D"http://kuhl.house.gov/blog/index.php/2008/05/16/fix-washington-pro=
ject/" target=3D_blank>Fix Washington</A>" project, where citizens =
proposed legislative priorities.=20
<LI>Senator Lieberman<SPAN>=E2=98=BC</SPAN> developed the first E-governmen=
t <A title=3DAct href=3D"http://www.whitehouse.gov/omb/egov/g-4-act.html" =
target=3D_blank>Act</A> of 2002 in conjunction with a <A title=3D"public =
Web site" href=3D"http://web.archive.org/web/20010603050357rn_1/www.senate.=
gov/~gov_affairs/egov/" target=3D_blank>public Web site</A> that collected =
priorities and suggestions. &nbsp;From the accompanying report language: =
</LI></UL></DIV></DIV>
<P style=3D"MARGIN-LEFT: 1in; TEXT-INDENT: -0.25in"><SPAN style=3D"FONT-SIZ=
E: 10pt"><SPAN>o<SPAN>&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN>On May 18, =
2000, Senators <SPAN>Lieberman</SPAN> and Thompson launched an on-line =
`experiment in interactive legislation', a website that sought public =
comments on 44 topics related to possible measures that Congress could =
take to advance the cause of <SPAN>e</SPAN>-government. Topics were =
organized into categories, such as `centralized leadership', `funding =
innovations', and `digital democracy: citizen access and participation,' =
and ranged from `centralized online portal' to `interoperability standards'=
 to `G-Bay': enhanced online distribution of federal government surplus =
property.' For each of the topics, a short discussion described the status =
of current efforts and the `New Idea', or ideas, being offered for =
consideration. Visitors to the website could then submit their comments on =
the subject, and read views that had been submitted by others. Nearly =
1,000 comments were submitted, approximately one half of which were posted =
on the website after being reviewed by Committee staff.13</P>
<DIV class=3DIh2E3d>
<P style=3D"MARGIN-LEFT: 1in">[Footnote] Comments were submitted by =
private citizens, academicians, federal employees, and even federal =
agencies. OMB also responded to the website by soliciting views from =
federal agencies; OMB officials then consolidated agencies' responses and =
presented them to the Committee as a single document. Opinions, additional =
information, and alternative proposals submitted over the website proved =
helpful as Senator <SPAN>Lieberman</SPAN> formulated his electronic =
government legislation.</P>
<P style=3D"MARGIN-LEFT: 1in">[Footnote] 13Comments were reviewed =
primarily for appropriateness and relevance; Committee staff did not favor =
any particular viewpoint in deciding which submissions to post. The =
website was intended to educate the public about the potential of =
<SPAN>e</SPAN>-government, to solicit input and information on the many =
topics being considered for possible legislation, and to serve as both an =
experiment and an example of how the Internet could be used to make =
government processes more accessible to the public.</P>
<UL type=3Ddisc>
<LI>Senator Dick Durbin<SPAN>=E2=98=BC</SPAN> held public discussions on =
<A title=3D"Open Left" href=3D"http://www.openleft.com/showDiary.do?diaryId=
=3D318" target=3D_blank>Open Left</A> and <A title=3DRedstate href=3D"http:=
//archive.redstate.com/stories/policy/what_should_we_include_in_our_nationa=
l_broadband_strategy" target=3D_blank>Redstate</A>, asking the question: =
"What Should We Include in our National Broadband Strategy?"=20
<LI>Politicopia is a public wiki, set up in conjunction with the Utah =
State Legislature's Rules Committee.=20
<LI>I'm looking for any other examples.&nbsp; Others that sort of fit: =
<BR><BR></LI></UL>
<UL type=3Ddisc>
<UL type=3Dcircle>
<LI>In a sense, the California initiative <A title=3Dprocess href=3D"http:/=
/www.cainitiative.org/" target=3D_blank>process</A> involves citizen =
participation, although it bypasses more than it augments the legislative =
process.=20
<LI>The <A title=3D"Peer to Patent Project" href=3D"http://www.peertopatent=
..org/" target=3D_blank>Peer to Patent Project</A> is probably the best =
designed example of substantive public involvement, although it isn't =
legislative. </LI></UL></UL>
<UL type=3Ddisc>
<LI>Any other suggestions? </LI></UL>
<P>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbs=
p; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbs=
p; &nbsp;&nbsp;&nbsp;&nbsp; </P></DIV></DIV>
<DIV class=3DIh2E3d>
<DIV><FONT size=3D2>-----Original Message----- <BR><B>From:</B> Sheridan, =
John [mailto:John.Sheridan@nationalarchives.gov.uk] <BR><B>Sent:</B> Sun =
07/09/2008 19:02 <BR><B>To:</B> Peter Krantz; public-egov-ig@w3.org =
<BR><B>Cc:</B> jeni@jenitennison.com; Appleby, Paul <BR><B>Subject:</B> =
RE: Legislation on the web...<BR><BR></FONT></DIV>
<P><FONT size=3D2>Peter,<BR><BR>I'm responsible for the development of the =
UK Government's "official legislation website" - and also for official =
Gazettes&nbsp; on the web (the London, Belfast and Edinburgh Gazettes).<BR>=
<BR>See: <A href=3D"http://www.opsi.gov.uk/acts/acts2008/ukpga_20080003_en_=
1">http://www.opsi.gov.uk/acts/acts2008/ukpga_20080003_en_1</A> for an =
example of how we publish legislation (it is semantic HTML and we use a =
bit of GRDDL too). We've published our XML Schema here: <A href=3D"http://w=
ww.opsi.gov.uk/legislation/schema/">http://www.opsi.gov.uk/legislation/sche=
ma/</A><BR><BR>You might also be interested in "Sem Webbing the London =
Gazette"<BR><A href=3D"http://2008.xtech.org/public/schedule/detail/528">ht=
tp://2008.xtech.org/public/schedule/detail/528</A><BR><BR>We're really =
keen to share ideas!<BR><BR>I've cc'ed some of the others involved.<BR><BR>=
John Sheridan<BR><BR>Head of e-Services<BR>Office of Public Sector =
Information<BR>Admiralty Arch<BR>North Side<BR>The Mall<BR>London<BR>SW1A =
2WH<BR><BR>Tel: 020 7276 5205<BR>Fax: 020 7276 2661</FONT></P>
<P style=3D"MARGIN-BOTTOM: 12pt">&nbsp;</P>
<P style=3D"MARGIN-BOTTOM: 12pt">&nbsp;</P>
<DIV>
<P>On Sun, Sep 7, 2008 at 1:19 PM, Peter Krantz &lt;<A href=3D"mailto:peter=
..krantz@gmail.com" target=3D_blank>peter.krantz@gmail.com</A>&gt; =
wrote:</P>
<P style=3D"MARGIN-BOTTOM: 12pt"><BR>Dear egov-ig group members,<BR><BR>Is =
there anyone else that is involved in a project that aims to put<BR>your =
national legislation on the web? We are currently half way<BR>through a =
project where we use a lot of W3C standards/technology (e.g.<BR>RDFa, OWL, =
RDFS, XHTML et al) to put swedish legislation online in a<BR>better shape =
than what exists today.<BR><BR>I was thinking that projects of this type =
would be similar (from a<BR>technology perspective) in many countries and =
it would be interesting<BR>to share ideas.<BR><BR>Kind regards,<BR><SPAN =
style=3D"COLOR: rgb(136,136,136)"><BR>Peter Krantz</SPAN></P></DIV>
<P>&nbsp;</P></DIV></DIV>
<P>&nbsp;</P></DIV></DIV></DIV></DIV></BLOCKQUOTE></DIV><BR></DIV></BODY></=
HTML>

--=__Part193094F0.4__=
Content-Type: IMAGE/gif; name="IMAGE.gif"
Content-Transfer-Encoding: base64
Content-ID: <CFTNEVTKFLFS.gears_online.gif>
Content-Description: CompuServe GIF graphic

R0lGODlhCwALAPMAAFHGKVLGKsXrucrtvkvFIvX781PGLFXHL/f89fD67cntvVLGK////1XHLgAA
AAAAACH5BAAAAAAALAAAAAALAAsAAAQ2kKVxmm0qMbSW7d6CKF7DnJ8SlCfzAQeLNosRt3jdmTht
EDIXDSDYmT4LRcF46SBOioslw4gAADs=

--=__Part193094F0.4__=
Content-Type: IMAGE/jpeg; name="IMAGE.jpeg"
Content-Transfer-Encoding: base64
Content-ID: <NGXRZVKRBPHJ.IMAGE.jpeg>
Content-Description: JPEG image

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAmADADASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD2avLP
iD4z1i18Svoen6lFpUEEAle4ZNzOSM46HH4V6nXknj/SNZsPHK+IbfS5NRsJYljljiBbcu3a6MBy
MjoaAMBvEfiZWYHxyoVTjdjOfyFRN4o8UohJ8ZfOEd9oIP3SeM4xk9R9amudf1m5xnwrcRlo5Ul8
u3YeZuQpH/D/AAKce9TS+KNYZ5Jl8JTJMXkYP9mYgho9gDjbhsDv3H50DKsfibxTJErjxoBkAkH+
HPr8vXn9DW54R8Z69b+KNO0+/wBXTVYNQYxshUBoT2OR9OnTBrGPiW7v9MmitPDV4kM23Y1qGKLt
RUxnbyPl9a3dDGt+LPF+l3kmhzafb6dcyXEkkwYAg9FBYZz0GBx3wKAJtY1f4jP4tvrLSxOlis5W
GQ2YZFX1ztJNM0rxL4ytPHunaHrOq206Tv8AvEgVDxg8HABU8dKvXbWn/CW34eG13eecsyW2fx3S
BvzFU9UVx8X9AZg20qNud2MYPTIxj/dJFAHqP2y2yB56ZJx1qOee0uIHga5CiUFCVbB544/PrXIf
8JREdSawfSLt5jM1u7GXIdw3zJnHPyAOPbiqqeMbe6shdtpMvyPFGm+5GFDE4VuMqRt6e/WgR31r
awWVrFa20SxQwqERFGAoFTVxsXj5ri9s7WHTBuu44iu6fG1nDYH3egK4z71vaDq02tWbXclkbRA5
jVXcMxKnDZx0G4ED1xmgC79htPNaX7LD5jHJfyxkn61y+t+FDc+ONF1u0EEX2ZmNzuZt0gx8uBjH
HPpRRQBuGDUGJzcRqJDn5RygPBxx1Axj3z60x7bUHiZvNhGQcrjgk9+nbj9fWiigA8i6jnCGYM54
R842j6Y5496t6eJRE4lbdhuDnJ980UUAf//Z

--=__Part193094F0.4__=--

--]W5x3Z--
Received on Thursday, 11 September 2008 08:03:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 11 September 2008 08:03:39 GMT