archive-edu.com » EDU » C » CORNELL.EDU

Total: 1513

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • United States Code in XML | LII / Legal Information Institute
    contracted Sept 08 Available from http voodoo law cornell edu uscxml Please notify Tom Bruce user Tom if you re planning on making use of this resource we would like you to give appropriate attribution and badge the site with one of our powered by badges Information about currency exists as a link from any of the US Code sections served from http www law cornell edu uscode and is Title specific A documented DTD is here http voodoo law cornell edu uscxml install United States Code background and resources up GPO locator code data standard Groups LexCraft LexCraft You must register login in order to post into this group This is an administered group if you re an author please login Toolbox Donations cover only 20 of our costs Law about Articles from Wex Fair Labor Standards Act Administrative Procedure Act Family and Medical Leave Act 1993 Clinton v City of New York 1998 Gibbons v Ogden 1824 Find a Lawyer All lawyers LexCraft Comments and contributions Legal Information Institute Cornell URIs for Courts OAI4Courts overview United States Code background and resources United States Code in XML GPO locator code data standard Section identifiers LII American legal citation Citations

    Original URL path: http://www.law.cornell.edu/wiki/lexcraft/united_states_code_in_xml (2012-11-09)
    Open archived version from archive


  • Section identifiers (LII) | LII / Legal Information Institute
    Clearly in the very new Title 6 it makes sense for chapter 1 to collect sections 101 through 103 plus some things called subchapters a different subject entirely chapter 2 to collect section 701 and some subchapters and chapter 3 to collect section 901 and some subchapters Yes the subchapters have something to do with the strange chapter level section number jumps So what is really clear is that when it comes to labeling things we have nothing to clarify but clarity itself But you knew that by looking in your spare closet Effect of Insertions new stuff happens in the middle The vigorous mouse clickers amongst you have already noticed something very important in the middle of the Title 1 Chapter 2 section number sequence 101 102 103 104 105 106 oops 106a 106b 107 I just made up the explicit oops of course but it really is in there see the notes to learn the formal spelling of oops 1951 Act Oct 31 1951 ch 655 2 a 65 Stat 710 added items 106a and 106b Title 1 is very small and quite stable but old enough to have some of the insertion effect on section numbers so called namely alphabetic extensions How far does this go in big old unstable titles Pretty far but there seems to be some system to it Past performance does not guarantee future results but so far we ve gotten away with the following based on careful rummaging through the 50 000 A championship real section number is 12 USC 1749bbb 10c which indicates a third level insertion The challenge is to make an efficient index to answer questions like the following Does this section number exist If not what is the closest that does exist What is its predecessor or successor What is its container chapter etc Oh but isn t this what XML gives us almost for free Yes once you have the XML A project is underway to make the content sources be XML but for now the best sources are the data that are used to typeset the print volumes Analysis of the present set of all US Code section numbers indicates that the following four part template is barely adequate 1 base six decimal digit integer 2 ext1 four character alphabetic field 3 ext2 three decimal digit integer 4 ext3 one character alphabetic field This yields with zero or dash filling of fields the following version of 1749bbb 10c 001749 bbb010c which naturally collates on most systems notice the dash in the normalized version is a fill character and unrelated to the hyphen in the raw number So what about that hyphen in the wild section number Our current working principle is that it is obligatory if there is an extension 2 Extension 1 is not obligatory for extension 2 which combined with the required hyphen means ambiguity when certain literature uses the dash in a range citation Inside the US Code the word to is used

    Original URL path: http://www.law.cornell.edu/wiki/lexcraft/section_identifiers_lii (2012-11-09)
    Open archived version from archive

  • Unqualified Dublin Core for judicial opinion metadata | LII / Legal Information Institute
    list of case identifiers disposed of or decided by the item Typically in the US this would be a list of docket numbers Note that this is intended to be a list of identifiers ONLY not eg a list of case titles or other descriptive information dc publisher Used to encode the publisher if distinct from the repository operator Note that the court or official body is actually represented by the dc coverage element This is a Dublin Core idiosyncrasy but unambiguous dc contributor Sitting judge not the primary author of the document Use of this element is ambiguous in situations where an item contains sub documents that are separately authored and no authorship status should be inferred from it in such a case dc date Official date of decision of the judgment ISO8601 YYYY MM DD format is expected dc type The Type element should only be used when the item is part of a compound dissemination Valid contents might include Majority opinion dissent concurrence syllabus erratum and so on Intelligent harvesters may then use the Relation element to identify other parts of the same dissemination dc format MIME type of the associated computer file eg PDF word processing formats etc dc identifier Multiple identifier elements may be used Minimally there must be an Identifier element specifying the fully qualified URI of the resource for retrieval or indexing purposes Additional identifier elements may be used to specify eg print citation or other official identifiers such as docket numbers dc source Not used Likely confused with the Relation element which see dc language Language used dc relation Used to encode related documents The content of the element should be a URI The URI may point to versions of this item in other languages or to other items that are components

    Original URL path: http://www.law.cornell.edu/wiki/lexcraft/unqualified_dublin_core_for_judicial_opinion_metadata (2012-11-09)
    Open archived version from archive

  • Standards development roadmap: American judicial opinion metadata | LII / Legal Information Institute
    a pretty good job of providing basic metadata but it s ruthless about what it leaves out Its priorities are also cheerfully and unashamedly biased in favor of the common law system in general and the American Federal court system in particular Second develop an XML schema that will represent caselaw metadata without the compromises that were necessary in the first scheme but still stay within reasonable bounds By reasonable bounds we mean using only data that most courts and publishers can easily cross walk from their existing publishing and case management systems That means on the one hand that we should work on eg more sophisticated representations of the participants in a case but on the other hand stop short of representations that require a lot of work in standardization such as representing the procedural posture of a case This Layer 2 schema can be thought of as a workhorse schema easy to make work with existing data collections not imposing huge burdens and avoiding lengthy standards wrangling in the interest of getting something out there that people can use Layer 2 is intended to do a better job that Layer One could at representing all the actors in a case judges parties and their representatives pulling in other sorts of case related literature such as briefs answering any systemic objections to Level One s cheerful bias in favor of the common law system in general and American courts in particular Third develop a series of idiosyncratic schemas that represent whatever people want Good targets for these Layer 3 schemas would be representation of nationalisms having to do with procedural matters or with the structure of the court system more sophisticated representation of procedural posture in general more sophisticated representation of citation and other crossreferencing systems Some implications Also

    Original URL path: http://www.law.cornell.edu/wiki/lexcraft/standards_development_roadmap_american_judicial_opinion_metadata (2012-11-09)
    Open archived version from archive

  • Software requirements for current implementation | LII / Legal Information Institute
    Different database packages may also require the installation of more Ruby gems it s possible that you ve already done this as part of the Ruby installation process mySQL setup Rails has a built in library that connects it with mySQL It s slow and according to the Rails developers unsuited for production use So you ll probably want to begin by installing the more robust version which is packaged as a gem gem install mysql If the installer complains that it needs to know more about your mySQL installation you can give it options like this gem install mysql with mysql lib usr lib mysql Note the presence of the extra dashes Next create the database at the command line we re calling it oai production mysqladmin u somebody p create oai production Then you d make a user we call her oai user and grant them rights on the database grant all on oai production to oai user identified by secretpassword You can then test access using the mysql command line client There is no need to create anything further in the database this will be handled as part of the Rails setup contributions of similar setup information for postgres Oracle and SQL Server would be highly appreciated Obtaining and setting up oai4courts itself Download oai4courts via anonymous subversion Decide where you d like to put your code it doesn t have to be in an existing web tree This documentation assumes that you re going to end up with all the code in usr local OAI current To start with just cd to the parent directory subversion will take care of creating the subdirectory structure in a minute cd usr local Now check out the source code There are two branches you need only run one of the following commands not both The first will get you the current stable version the second has the often broken development version svn co svn chrome law cornell edu OAI current OR you probably don t want this Don t say we didn t warn you svn co svn chrome law cornell edu OAI Connect oai4courts with your database setup Next you ll need to tell oai4courts about your database server Copy the example configuration file to its proper location cd OAI current config initializers cp database yml example database yml Now you ll need to edit it The simplest way is to change the production setup to reflect your database installation production adapter mysql database oai production timeout 5000 username oai user password secretpassword Initialize the databases Make sure that you re in the root directory of your oai4courts installation then run the Rails migration that sets up the database cd usr local OAI current export RAILS ENV production rake db migrate You should see a stream of messages showing the creation of many tables within the database mySQL users if the script complains that it can t find mysql sock you can add a line like this to

    Original URL path: http://www.law.cornell.edu/wiki/lexcraft/software_requirements_for_current_implementation (2012-11-09)
    Open archived version from archive

  • Sets and tags | LII / Legal Information Institute
    organization of the oai sets table in the database which has the following elements set spec the OAI setSpec element which specifies an identifier for the set as well as showing its place in the hierarchy of sets set name the OAI setName element which provides a short human readable name for the set description the OAI setDescription element which describes the set set type a hint about the process used to construct the set query a hint about what the processor should process The last two elements which are specific to oai4courts can be used to specify a processing regime for population of the set by an external utility program or script For example a set type of supct full text and a query value of civil rights might indicate that members of the set with this id could be found by firing a fulltext search on the supct corpus using the query string civil rights Or the set type might indicate that a particular relational database holds relevant information and the query element might contain a SQL query that when fired against that database would retrieve a list of set members for incorporation into the decisions oai sets table In other words the two fields simply allow the repository operator to store hints about what process and query should be used to identify members of the set The hints and processes are entirely arbitrary and are assumed to be run by external utilities when the decisions oai sets table is to be populated Tags and the database As of this writing little has been done to support tagging other than the provision of appropriate tables in the database Not what you would call a fully thought through feature Porting data overview up OAI bibliography Groups LexCraft LexCraft You

    Original URL path: http://www.law.cornell.edu/wiki/lexcraft/sets_and_tags (2012-11-09)
    Open archived version from archive

  • OAI bibliography | LII / Legal Information Institute
    S Courts of Appeals Getting started as an author Legal research Find a Lawyer All lawyers LexCraft Comments and contributions Legal Information Institute Cornell URIs for Courts OAI4Courts overview Standards development roadmap American judicial opinion metadata Open Archives Initiative Approach to the OAI4courts standard Layer one approach and compromises Layer two overview Cases Orders Opinions Decisions and Writings Caselaw identifiers for oai4courts Database schemas and documentation Unqualified Dublin Core for

    Original URL path: http://www.law.cornell.edu/wiki/lexcraft/oai_bibliography (2012-11-09)
    Open archived version from archive

  • Ruby on Rails customization for oai4courts | LII / Legal Information Institute
    Lawyer All lawyers LexCraft Comments and contributions Legal Information Institute Cornell URIs for Courts OAI4Courts overview Standards development roadmap American judicial opinion metadata Open Archives Initiative Approach to the OAI4courts standard Layer one approach and compromises Layer two overview Cases Orders Opinions Decisions and Writings Caselaw identifiers for oai4courts Database schemas and documentation Unqualified Dublin Core for judicial opinion metadata Qualified Dublin Core citation example Software requirements for current implementation

    Original URL path: http://www.law.cornell.edu/wiki/lexcraft/ruby_on_rails_customization_for_oai4courts (2012-11-09)
    Open archived version from archive



  •