Misplaced Pages

#928071

42-609: The European Case Law Identifier (ECLI) is an identifier for court decisions in Europe. The identifier consists of five elements separated by colons: ECLI: [country code] : [court identifier] : [year of decision] : [specific identifier] . The standard is laid down in the Council Conclusions inviting the introduction of the European Case Law Identifier (ECLI) and a minimum set of uniform metadata for case law of

84-721: A decision from the Czech Supreme Court, the information from the website of that court as well as from the Jurifast database of the Association of Councils of State and Supreme Administrative Jurisdictions of the EU . The latter document also has English and French metadata. Documents are indexed by the ECLI search engine in cooperation between the European Commission and data providers, using

126-556: A good case example in a recent-decades, technical-nomenclature context. The capitalization variations seen with specific designators reveals an instance of this problem occurring in natural languages , where the proper noun/common noun distinction (and its complications) must be dealt with. A universe in which every object had a UID would not need any namespaces, which is to say that it would constitute one gigantic namespace; but human minds could never keep track of, or semantically interrelate, so many UIDs. Sitemaps This

168-540: A judicial decision. They can relate to the ECLI itself (on the bibliographic work level, e.g.: date of the decision), but also to a specific editorial version (the 'expression level', e.g. a summary). In the Council Conclusions nine mandatory and eight optional metadata are listed. All these are based on the Dublin Core metadata standard . The mandatory means that without these metadata, a document can not be indexed by

210-402: A sitemap index file (a file that points to multiple sitemaps). A syndication feed is a permitted method of submitting URLs to crawlers; this is advised mainly for sites that already have syndication feeds. One stated drawback is this method might only provide crawlers with more recently created URLs, but other URLs can still be discovered during normal crawling. It can be beneficial to have

252-406: A syndication feed as a delta update (containing only the newest content) to supplement a complete sitemap. If Sitemaps are submitted directly to a search engine ( pinged ), it will return status information and any processing errors. The details involved with submission will vary with the different search engines. The location of the sitemap can also be included in the robots.txt file by adding

294-559: A website, but that are hosted externally, such as on Vimeo or YouTube . Image sitemaps are used to indicate image metadata, such as licensing information, geographic location, and an image's caption. Google supports a Google News sitemap type for facilitating quick indexing of time-sensitive news subjects. In December 2011, Google announced the annotations for sites that want to target users in many languages and, optionally, countries. A few months later Google announced, on their official blog, that they are adding support for specifying

336-434: Is a language-independent label, sign or token that uniquely identifies an object within an identification scheme . The suffix "identifier" is also used as a representation term when naming a data element . ID codes may inherently carry metadata along with them. For example, when you know that the food package in front of you has the identifier "2011-09-25T15:42Z-MFR5-P02-243-45", you not only have that data, you also have

378-455: Is an accepted version of this page ‹The template Manual is being considered for merging .›   Sitemaps is a protocol in XML format meant for a webmaster to inform search engines about URLs on a website that are available for web crawling . It allows webmasters to include additional information about each URL: when it was last updated, how often it changes, and how important it

420-513: Is based on ideas from "Crawler-friendly Web Servers," with improvements including auto-discovery through robots.txt and the ability to specify the priority and change frequency of pages. Sitemaps are particularly beneficial on websites where: The Sitemap Protocol format consists of XML tags. The file itself must be UTF-8 encoded. Sitemaps can also be just a plain text list of URLs. They can also be compressed in .gz format. A sample Sitemap that contains just one URL and uses all optional tags

462-429: Is essential for any kind of symbolic processing. In computer languages , identifiers are tokens (also called symbols ) which name language entities. Some of the kinds of entities an identifier might denote include variables , types , labels , subroutines , and packages . A resource may carry multiple identifiers. Typical examples are: The inverse is also possible, where multiple resources are represented with

SECTION 10

#1732845456929

504-520: Is in relation to other URLs of the site. This allows search engines to crawl the site more efficiently and to find URLs that may be isolated from the rest of the site's content. The Sitemaps protocol is a URL inclusion protocol and complements robots.txt , a URL exclusion protocol. Google first introduced Sitemaps 0.84 in June 2005 so web developers could publish lists of links from across their sites. Google, Yahoo! and Microsoft announced joint support for

546-542: Is often referred to as a code or id code . For instance the ISO/IEC 11179 metadata registry standard defines a code as system of valid symbols that substitute for longer values in contrast to identifiers without symbolic meaning. Identifiers that do not follow any encoding scheme are often said to be arbitrary Ids ; they are arbitrarily assigned and have no greater meaning. (Sometimes identifiers are called "codes" even when they are actually arbitrary, whether because

588-637: Is only used to suggest to the crawlers how important pages of the site are to one another. Does not apply to <sitemap> elements. Support for the elements that are not required can vary from one search engine to another. The Sitemaps protocol allows the Sitemap to be a simple list of URLs in a text file. The file specifications of XML Sitemaps apply to text Sitemaps as well; the file must be UTF-8 encoded, and cannot be more than 50MiB (uncompressed) or contain more than 50,000 URLs. Sitemaps that exceed these limits should be broken up into multiple sitemaps with

630-449: Is shown below. The Sitemap XML protocol is also extended to provide a way of listing multiple Sitemaps in a 'Sitemap index' file. The maximum Sitemap size of 50  MiB or 50,000 URLs means this is necessary for large sites. An example of Sitemap index referencing one separate sitemap follows. The definitions for the elements are shown below: "Always" is used to denote documents that change each time that they are accessed. "Never"

672-424: Is used to denote archived URLs (i.e. files that will not be changed again). This is used only as a guide for crawlers , and is not used to determine how frequently pages are indexed. Does not apply to <sitemap> elements. The valid range is from 0.0 to 1.0, with 1.0 being the most important. The default value is 0.5. Rating all pages on a site with a high priority does not affect search listings, as it

714-461: The German tank problem ). Opaque identifiers—identifiers designed to avoid leaking even that small amount of information—include "really opaque pointers " and Version 4 UUIDs . In computer science , identifiers (IDs) are lexical tokens that name entities . Identifiers are used extensively in virtually all information processing systems. Identifying entities makes it possible to refer to them, which

756-575: The identifier "Model T" identifies the class (model) of automobiles that Ford's Model T comprises; whereas the unique identifier "Model T Serial Number 159,862" identifies one specific member of that class—that is, one particular Model T car, owned by one specific person. The concepts of name and identifier are denotatively equal, and the terms are thus denotatively synonymous ; but they are not always connotatively synonymous, because code names and Id numbers are often connotatively distinguished from names in

798-584: The sitemaps protocol and robots.txt . The Council of Ministers is responsible for any future changes in the standard, while the European Commission is responsible for the ECLI-website and the maintenance of the ECLI Search Engine. Every Member State (or other entity that wishes to participate in the ECLI system, including the EU itself) must have a national ECLI co-ordinator. The main responsibilities of this national ECLI co-ordinator are: According to

840-590: The Annex to the Council Conclusions an ECLI website has to be set up, containing The ECLI website was set up within the frame work of the e-justice portal of the European Union. According to paragraph 5 of the Annex to the Council Conclusions an ECLI Search Engine has to be set up, enabling search by ECLI and metadata. This ECLI search engine launched on 4 May 2016. It provides access to national and European case law, stored in whatever database. Searches are possible on

882-610: The Annex to the Council Conclusions. Summarized, an ECLI always consists of five parts, separated by a colon: Only the Latin alphabet is to be used, and that ECLI is case-insensitive, although it is written preferably in capitals. An example of a case law identifier of the Dutch Supreme Court is ECLI:NL:HR:1841:1, which indicates a Dutch decision (NL) of 1841 of the Supreme Court (HR) with serial number 1. According to paragraph 4 of

SECTION 20

#1732845456929

924-584: The Council Conclusion inviting the introduction of the European Case Law Identifier (ECLI) and a minimum set of uniform metadata for case law of the European Union, decided upon by the Council of Ministers on 22 December 2010. It was published in the Official Journal of 29 April 2011 (2011/C 127/01). ECLI does not primarily identify a paper or electronic document containing a judgment, but instead identifies

966-681: The Council Conclusions, Member States are free to decide on their own implementation route. A big-bang scenario is possible, but also a step-by-step approach is allowed. International organizations may also participate and can request a "country code" from the European Commission. The table below lists all EU Member States and their current state of ECLI implementation. Also relevant European organisations that have implemented ECLI are included. State or European organisation in public database ECLI going live co-ordinator ECLI Search Engine decisions indexed (rounded, as of 30-05-2019) Metadata are to be attached to documents containing

1008-457: The ECLI Search Engine. The mandatory metadata, as listed in the Annex to the Council Conclusions, are: The optional metadata, as listed in the Annex to the Council Conclusions, are: Identifier The words, numbers, letters, or symbols may follow an encoding system (wherein letters, digits, words, or symbols stand for [represent] ideas or longer names) or they may simply be arbitrary. When an identifier follows an encoding system, it

1050-471: The EU. In addition a Dublin-core implementation for case-law should be established to facilitate searching case-law in different search engines. Based on the report of this task group, the Council of Ministers agreed on the principles of ECLI and common metadata, and asked the EU Council Working Party on Legal Data Processing (e-Law) to elaborate the initial work. This continued work resulted in

1092-663: The European Union. The ECLI framework also contains a set of uniform metadata to improve search facilities for case law. Court decisions that have an ECLI assigned can be indexed by the ECLI Search Engine of the European e-Justice portal . The concept of ECLI was first launched at the Legal Access Conference (Paris, December 2008) and at Jurix Conference on Artificial Intelligence and Law in Florence (December 2008). Around

1134-533: The Sitemaps protocol in November 2006. The schema version was changed to "Sitemap 0.90", but no other changes were made. In April 2007, Ask.com and IBM announced support for Sitemaps. Also, Google, Yahoo, MSN announced auto-discovery for sitemaps through robots.txt . In May 2007, the state governments of Arizona, California, Utah and Virginia announced they would use Sitemaps on their web sites. The Sitemaps protocol

1176-414: The basis of the ECLI, its metadata as well as full-text. As prescribed by the Council Conclusions a resolver is available at https://e-justice.europa.eu/ecli/; with an ECLI typed after it, this link with show all available information on this ECLI, from whatever indexed website. As an example: https://e-justice.europa.eu/ecli/ECLI:CZ:NS:2015:32.CDO.2051.2013.1 shows from ECLI:CZ:NS:2015:32.CDO.2051.2013.1 ,

1218-408: The characters ampersand (&), single quote ('), double quote ("), less than (<), and greater than (>). Best practice for optimising a sitemap index for search engine crawlability is to ensure the index refers only to sitemaps as opposed to other sitemap indexes. Nesting a sitemap index within a sitemap index is invalid according to Google. A number of additional XML sitemap types outside of

1260-482: The court decision at a more abstract level. In the terminology of the Functional Requirements for Bibliographic Records on which it is based, ECLI is a work-level identifier. It is constructed with the intention to be meaningful, open, technological neutral, recognisable for both humans and computers, error-proof and interoperable with other identifiers. The formatting rules for ECLI are prescribed in detail in

1302-449: The following line: The <sitemap_location> should be the complete URL to the sitemap, such as: This directive is independent of the user-agent line, so it doesn't matter where it is placed in the file. If the website has several sitemaps, multiple "Sitemap:" records may be included in robots.txt , or the URL can simply point to the main sitemap index file. The following table lists

European Case Law Identifier - Misplaced Pages Continue

1344-683: The metadata that tells you that it was packaged on September 25, 2011, at 3:42pm UTC, manufactured by Licensed Vendor Number 5, at the Peoria, IL, USA plant, in Building 2, and was the 243rd package off the line in that shift, and was inspected by Inspector Number 45. Arbitrary identifiers might lack metadata. For example, if a food package just says 100054678214, its ID may not tell anything except identity—no date, manufacturer name, production sequence rank, or inspector number. In some cases, arbitrary identifiers such as sequential serial numbers leak information (i.e.

1386-434: The original naming convention, which had formerly been latent and moot, become painfully apparent, often necessitating retronymy , synonymity , translation/ transcoding , and so on. Such limitations generally accompany the shift away from the original context to the broader one. Typically the system shows implicit context (context was formerly assumed, and narrow), lack of capacity (e.g., low number of possible IDs, reflecting

1428-447: The outmoded narrow context), lack of extensibility (no features defined and reserved against future needs), and lack of specificity and disambiguating capability (related to the context shift, where longstanding uniqueness encounters novel nonuniqueness). Within computer science, this problem is called naming collision . The story of the origination and expansion of the CODEN system provides

1470-487: The rel="alternate" and hreflang annotations in Sitemaps. Instead of the (until then only option) HTML link elements the Sitemaps option offered many advantages which included a smaller page size and easier deployment for some websites. One example of the multilingual sitemap would be as follows: If for example we have a site that targets English language users through https://www.example.com/en and Greek language users through https://www.example.com/gr , up until then

1512-406: The same identifier (discussed below). Many codes and nomenclatural systems originate within a small namespace . Over the years, some of them bleed into larger namespaces (as people interact in ways they formerly had not, e.g., cross-border trade, scientific collaboration, military alliance, and general cultural interconnection or assimilation). When such dissemination happens, the limitations of

1554-743: The same time, the study by a task group of the EU Council Working Group on e-Law showed that accessibility of judicial decisions, both at the national and European level, was seriously hampered by the lack of standardised identifiers and metadata: The task group suggested to establish a voluntary common identification system based on the European Case-Law Identifier (ECLI). ECLI as an identifier would be linked to an index with references. This would enable any citizen or legal practitioner to find any decision to which ECLI has been attributed from any public or private register or database in

1596-516: The scope of the Sitemaps protocol are supported by Google to allow webmasters to provide additional data on the content of their websites. Video and image sitemaps are intended to improve the capability of websites to rank in image and video searches. Video sitemaps indicate data related to embedding and autoplaying, preferred thumbnails to show in search results, publication date, video duration, and other metadata. Video sitemaps are also used to allow search engines to index videos that are embedded on

1638-467: The sense of traditional natural language naming. For example, both " Jamie Zawinski " and " Netscape employee number 20" are identifiers for the same specific human being; but normal English-language connotation may consider "Jamie Zawinski" a "name" and not an "identifier", whereas it considers "Netscape employee number 20" an "identifier" but not a "name." This is an emic indistinction rather than an etic one. In metadata, an identifier

1680-471: The sitemap submission URLs for a few major search engines: Sitemap URLs submitted using the sitemap submission URLs need to be URL-encoded , for example: replace : (colon) with %3A , replace / (slash) with %2F . Sitemaps supplement and do not replace the existing crawl-based mechanisms that search engines already use to discover URLs. Using this protocol does not guarantee that web pages will be included in search indexes, nor does it influence

1722-405: The speaker believes that they have deeper meaning or simply because they are speaking casually and imprecisely.) The unique identifier ( UID ) is an identifier that refers to only one instance —only one particular object in the universe. A part number is an identifier, but it is not a unique identifier—for that, a serial number is needed, to identify each instance of the part design. Thus

European Case Law Identifier - Misplaced Pages Continue

1764-592: The way that pages are ranked in search results. Specific examples are provided below. Sitemap files have a limit of 50,000 URLs and 50 MiB (52,428,800 bytes) per sitemap. Sitemaps can be compressed using gzip , reducing bandwidth consumption. Multiple sitemap files are supported, with a Sitemap index file serving as an entry point. Sitemap index files may not list more than 50,000 Sitemaps and must be no larger than 50MiB and can be compressed. You can have more than one Sitemap index file. As with all XML files, any data values (including URLs) must use entity escape codes for

#928071