150 likes | 327 Views
REGNET. An Information Infrastructure for Comparing Accessibility Regulations and Related Information from Multiple Sources. Gloria Lau Kincho Law Engineering Informatics Group, Stanford University. Motivation. Multiple sources of regulations
E N D
REGNET An Information Infrastructure for Comparing Accessibility Regulations and Related Information from Multiple Sources Gloria Lau Kincho Law Engineering Informatics Group, Stanford University
Motivation • Multiple sources of regulations • Multiple jurisdictions: federal, state, local, etc. • Different formats, terminologies, contexts • Amending rules, conflicting ideas Need for a repository • Locate relevant information • E.g., small business: penalty fees for violations Need for analysis tool • Complexity of regulations • Multiple jurisdictions • Understanding of regulations & their relationships
Example: Related but Conflicting Provisions ADAAG 4.7.2 Slope. …Transitions from ramps to walks, gutters, or streets shall be flush and free of abrupt changes… CBC 1127B.5.5 Beveled lip. The lower end of each curb ramp shall have a ½ inch (13mm) lip beveled at 45 degrees as a detectable way-finding edge for persons with visual impairments. • ADAAG focuses on wheelchair traversal; CBC focuses on the visually impaired when using a cane.
Scope • Repository development • Relatedness analysis • Results and applications Relatedness analysis Repository development
Digital publication of regulations • Current standard: HTML, PDF, plain text... • Our system standard: XML • Recreate regulatory structure • Unit of extraction: section/provision • Extract references • Extract features <regulation id="ibc" name="international building code" type="private"> <regElement id="ibc.1107" name="special occupancies"> … <regElement id="ibc.1107.2" name=“assembly area seating"> <reference id="ibc.1107.2.4.1" times="1" /> <concept name="assembl area" times="1" /> … <regText>Assembly areas with fixed seating shall comply … </regText> <regElement id="ibc.1107.2.1" name="services">...</regElement> <regElement id="ibc.1107.2.2" name=“wheelchair …">...</regElement> </regElement> </regElement> </regulation>
Feature Extraction Original Section 4.6.3 from the UFAS 4.6.3* PARKING SPACES. Parking spaces for disabled people shall be at least 96 in (2440 mm) wide and shall have an adjacent access aisle 60 in (1525 mm) wide minimum (see Fig. 9). Parking access aisles shall be part of ... EXCEPTION: … an adjacent access aisle at least 96 in (2440 mm) wide complying with 4.5... Refined Section 4.6.3 in XML format <regElement name=”ufas.4.6.3” title=”parking spaces” asterisk=”1”> <concept name=”access aisl” num=”3” /> … <indexTerm name=”park space” num=”4” /> <measurement unit=”inch” magnitude=”96” quantifier=”min” /> <ref name=”ufas.4.5” num=”1” /> <regText> Parking spaces for disabled people shall ... </regText> <exception> If accessible parking spaces for ... </exception> </regElement>
Relatedness analysis ADAAG 4.1.6(3)(d) Doors (i) Where it is technically infeasible to comply with clear opening width requirements of 4.13.5, a projection ... UFAS 4.14.1 Minimum Number Entrances required to be accessible by 4.1 shall be part of an accessible route and shall comply with ... Related elements: door and entrance
Relatedness analysis • Base Score f0 • Linear combination of features • Neighbor inclusion • Diffusion of similarity between clusters of nodes • Reference distribution • Diffusion of similarity between referenced nodes and referencing nodes f (0, 1)
Results of comparisons : UFAS vs. BS8300 • Terminological differences - revealed through neighbor inclusion
Application: e-rulemaking • Application domain: e-rulemaking • Comparison between draft of rules and the associated public comments • ADAAG Chapter 11, rights-of-way draft • Less than 15 pages • Over 1400 public comments received within 4 months • Comments ~10MBin size; most are several pages long New regulation draft can easily generate a huge amount of data that needs to be reviewed and analyzed • Parsing of the draft and comments • From HTML to XML • Recreate structure of the draft using our shallow parser • Extract features from the draft and comments • Treat individual comments as provisions
E-rulemaking Drafted regulations compared with public comments
Conclusions • A framework for regulatory repository • Structure of regulations recreated in XML • Feature extractions • Prototype for similarity comparisons • Contextual comparisons • Domain knowledge • Structural comparisons • Results and Applications • Example of comparison results between US codes and European standards • Application on e-rulemaking