...
The default format for exchanging metadata between institutional repositories and service providers is simple Dublin Core (DC). For many services based on harvesting repositories, this format has significant limitations. A well-known problem of simple Dublin Core is its lack of detail or granularity. Granularity is mentioned as the first of three requirements for metadata schemes by Beth Goldsmith and Frances Knudson in D-Lib Magazine of September 2006 (doi:10.1045/september2006-goldsmith). They introduce granularity as follows. "Widely considered the bedrock for metadata storage, granularity insures lossless data mapping without blurring the finer shades of meaning intrinsic to the original data. A granular standard must provide the ability to differentiate formats of description (e.g. different types of authors) and to maintain context and linkages among data elements." . Some examples of granularity problems with (Simple) Dublin Core are the following. The first example is that there are no separate elements for volume, issue and page; in order to identify them, a string has to be parsed. Second, it is not possible to describe in the same DC record the item of which a publication, e.g., a book chapter, is a part. A third example is that it is not possible to indicate the exact role of a creator or contributor. A last example is that it is not possible to include Digital Author Identifiers. This is necessary information for services that, e.g., want to offer OpenURL links or generate high quality publication lists. MODS (http://www.loc.gov/standards/mods/), that is the subject of this document, is a international standard that allows for describing publications at a much deeper level of detail than DC. It is especially suited for describing "traditional" publications like journal articles, books, book chapters, patents and reports Although MODS can also be used for materials other than publications, this document is restricted to the use of MODS for describing publications.. For a detailed description of other material like data sets different metadata standards have to be used.
...
For language codes, the guidelines of RFC 3066 (http://www.ietf.org/rfc/rfc3066.txt) must be followed. This means that the two-character ISO 639-1 codes are used; for those languages not in ISO 639-1, the three-character ISO 639-2 codes must be used. A complete list of these codes is available at http://en.wikipedAnchor
To indicate the language of the content of the elements the xml:lang attribute must be used and not the lang attribute. For each MODS element it is defined whether the language attribute xml:lang can be used. According to the XML standard xml:lang follows RFC 3066.
In the <language> element, the authority="rfc3066" indicates that RFC 3066 is applied.
Example: the language of the publication is Dutch
<language>
<languageTerm type="code" authority="rfc3066">nl</languageTerm>
</language>
Date format
For dates, iso8601 is the recommended standard. More in particular, the W3C profile should be used, see http://www.w3.org/TR/NOTE-datetime. A complete date has the form YYYY-MM-DD. Use the encoding attribute with value 'iso8601' to indicate the date format.
Example: date of promotion that a doctoral thesis is issued
<dateIssued encoding="iso8601">2007-03-09</dateIssued>
Root Element
...
...
...
...
...
...
mods
...
A single MODS record; the element modsCollection as wrapper of several MODS records must not be used
...
...
...
Attributes:
...
...
...
...
...
...
version
...
...
...
the MODS version, e.g., version="3.2"
...
Subelements:
...
...
...
...
...
...
See: http://www.loc.gov/standards/mods/v3/mods-3-3-outline-review.html#top_levelTop Level Elements
...
...
See: Top Level Elements
Top Level Elements
titleInfo
This element is required and is
...
...
...
...
...
a wrapper for information about the title of a publication. This is also used for the title of an host item like a journal or a series. There is at least one subelement title.
...
...
...
...
Attributes:
...
...
...
...
...
xml:lang
...
...
type
...
...
...
...
...
use only for the translated title, in that case the value is translated
...
displayLabel
...
...
...
...
can be used for the number of a report. Don't use for the number of a report in a series.
...
Subelements:
...
...
...
...
...
title
...
...
...
...
...
Required. Sub title can be included in this element and separated by a colon from the main title; it is recommended to use subTitle.
...
subTitle
...
...
name
...
...
...
...
...
...
...
...
...
This element contains information about the author or editor of the publication. It can also be used to give the name of the thesis advisor, a patent holder, a patent applicant or the sponsor. <name> is a wrapper element and has at least one namePart subelement. In most cases there will be at least two namePart elements; one for the family name and one for the given name.
In the case of theses for acquiring a degree, the name of the institution has to be included (use the same formatting as for affiliation, see name/affiliation below): <name type="corporate"><namePart>the granting university</namePart>
<role><roleTerm authority="marcrelator" type="code">dgg</roleTerm></role></name>
...
...
...
...
...
...
...
...
...
...
Attributes:
...
...
...
...
...
...
...
...
...
...
ID
...
...
...
...
...
...
...
...
...
...
...
...
use this ID to refer to the /mods/extension/daiList/idenifier element for the DAI of the author, see Annex:DAI schema. The ID must be a NCName: start with a letter or underscore, followed by zero or more characters (but no colons).
...
...
...
...
type
...
...
...
...
...
...
...
...
...
...
...
values: personal, corporate, conference
...
...
...
...
...
...
...
Subelements:
...
...
...
...
...
...
...
...
...
...
...
namePart
...
...
...
...
...
...
...
...
...
...
...
Attributes:
...
...
...
...
...
...
...
...
...
...
type
...
...
...
...
...
values: personal, corporate, conference
...
...
...
...
...
Subelements:namePart
Attributes:
type
...
...
values: family, given, termsOfAddress. 'infix' will be proposed as a valid value to the MODS maintenance agency. The intended use of 'infix' is for what is called in Dutch "het tussenvoegsel"; in 'Jan van de Meer' is 'Jan' the given name, 'van de' the infix and 'Meer' the family name. For the time being, it is advised to add the infix at the end of the family name, separated from the family name by a comma, e.g., <namePart type="family">Meer, van de</namePart>. For Belgian authors the infix ("tussenvoegsel") is part of the family name: <namePart type="family">Van de Meer</namePart>
When initial and full name are both available use this formatting:
<namePart type="given">J. (John)</namePart>
Use the value termsOfAddress only for generational suffixes like Jr. or Sr. Omit titles (like "prof" or "dr").
...
...
...
...
affiliation
...
...
...
...
...
...
...
...
...
...
Affiliation at the time of publication. Represented as a dot limited list starting with the name of the institution followed by organizational sub-units. The list follows the organizational hierarchy.
In the case of a conference, use affiliation for describing the location of the
...
...
...
...
...
...
...
...
role
...
...
...
...
...
...
...
...
...
...
...
Subelements:
...
...
...
...
...
...
...
...
...
...
roleTerm
...
...
...
...
...
...
...
...
...
conference.
role
Subelements:
roleTerm
...
...
use one of the three letter-codes of http://www.loc.gov/marc/sourcecode/relator/relatorlis
| Anchor | ||||
|---|---|---|---|---|
|
...
...
...
...
...
...
...
...
...
...
...
...
Attributes:
...
...
...
...
type
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
value: code
...
...
authority
...
...
...
...
...
...
...
...
...
value: marcrelator
...
|
| ||||||
| Use the value 'text' for publications: <typeOfResource>text</typeOfResource> |
...
Use for publication types identifiers from the info:eu-repo/semantics/ namespace, see the first column of the following table. E.g., the URI for articles is info:eurepo/semantics/article. The second column contains the vocabulary of the Eprints Application Profile (also known as Scholarly Works Application Profile - SWAP) (http://www.ukoln.ac.uk/reposito
| Anchor | ||||
|---|---|---|---|---|
|
info:eu-repo/semantics/ |  | Description |
|
|
|
annotation |
| note to a legal judgment |
article | JournalArticle | article in a journal |
bachelorThesis | Thesis (broader) | bachelor thesis |
book | Book | book or monograph. |
bookPart | BookItem | part or chapter of a book |
bookReview | BookReview | book review |
conferencePaper | ConferencePaper | paper published in conference proceedings |
contributionToPeriodical |
| contribution to a newspaper, weekly magazine or another non-academic periodical |
doctoralThesis | Thesis (broader) | PhD dissertation |
researchProposal |
| documentation for grant request |
lecture |
| Published lecture presented during an academic event, e.g., inaugural lecture |
masterThesis | Thesis (broader) |
|
patent | Patent | patent |
preprint | Report (broader) | like a research paper this is a preliminary scientific or technical paper, but it is not published in a institutional series. The paper is intended to be published in a scientific journal or as a chapter in a book. |
report | Report (broader) | this is a more or less a rest category and covers commission reports, memoranda, conference reports, external research reports, internal reports, statistical report, reports to funding agency, etc. |
studentThesis | Thesis (broader) | this refers to theses of the pre-Bologna period for degrees that are at the same level as what now is known as a master degree |
technicalDocumentation |
| technical documentation |
workingPaper | WorkingPaper | a preliminary scientific or technical paper that is published in a series of the institution where the research is done. Also known as research paper, research memorandum or discussion paper. The difference with a preprint is that a workingPaper is published in a institutional series. |
| ScholarlyText | all the other types are a sub-classe of this type |
| ConferenceItem | covers conference papers and conference posters |
| ConferencePoster | poster presented at a conference |
| JournalItem | a contribution to a journal; includes articles, editorials, conference reports, etc. |
| NewsItem | news item |
| SubmittedJournalArticle | the author's original manuscript submitted to and/or accepted by a journal. When not accepted it is a info:eu-repo/semantics/preprint or a info:eu-repo/semantics/workingPaper and when accepted it is a info:eu-repo/semantics/article |
...
<?xml version="1.0" encoding="UTF-8"?>
<!-- file: mods_article.xml ->
<mods
version="3.2"
xmlns="http://www.loc.gov/mods/v3"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.loc.gov/mods/v3
http://www.loc.gov/standards/mods/v3/mods-3-2.xsd">
<titleInfo xml:lang="en">
<title>Angioplasty of chronic total coronary occlusions with the use of six French guiding catheters</title>
</titleInfo>
<typeOfResource>text</typeOfResource>
<genre>info:eu-repo/semantics/article</genre>
<subject xml:lang="en">
<topic>coronary occlusion</topic>
<topic>angioplasty</topic>
<topic>French guiding catheters</topic>
</subject>
<abstract xml:lang="en">The efficacy of 6 French guiding catheters...</abstract>
<name type="personal" ID="n1">
<namePart type="family">Koch</namePart>
<namePart type="given">K.T.</namePart>
<role>
<roleTerm authority="marcrelator" type="code">aut</roleTerm>
</role>
</name>
<name type="personal" ID="n2">
<namePart type="family">Winter, de</namePart>
<namePart type="given">R.J.</namePart>
<role>
<roleTerm authority="marcrelator" type="code">aut</roleTerm>
</role>
</name>
<extension>
<daiList
xmlns:dai="info:eu-repo/dai"
xsi:schemaLocation="info:eu-repo/dai
http://www.surfgroepen.nl/sites/oai/metadata/Shared%20Documents/dai-extension.xsd">
<identifier
IDref="n2"
authority="info:eu-repo/dai/nl">157455590</identifier>
<identifier
IDref="n1"
authority="info:eu-repo/dai/nl">123456678</identifier>
</daiList>
</extension>
<originInfo>
<dateIssued encoding="iso8601">1997</dateIssued>
</originInfo>
<relatedItem type="host">
<identifier type="uri">URN:ISSN:00986569</identifier>
<titleInfo>
<title>Cathet. Cardiovasc. Diag.</title>
</titleInfo>
<part>
<detail type="volume"><number>40</number></detail>
<extent unit="page">
<start>255</start>
<end>260</end>
</extent>
</part>
</relatedItem>
</mods>
...
<?xml version="1.0" encoding="UTF-8"?>
<!-- file: artikel1_ubu_uitgebreid.xml ->
<mods
xmlns="http://www.loc.gov/mods/v3"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.loc.gov/mods/v3
http://www.loc.gov/standards/mods/v3/mods-3-2.xsd">
<titleInfo>
<title>Grooming behavior of spontaneously hypertensive rats</title>
</titleInfo>
<name type="personal">
<namePart type="given">M.</namePart>
<namePart type="family">Buuse</namePart>
<role>
<roleTerm authority="marcrelator" type="code">aut</roleTerm>
</role>
</name>
<name type="personal">
<namePart type="given">W.</namePart>
<namePart type="family">Jong, de</namePart>
<role>
<roleTerm authority="marcrelator" type="code">aut</roleTerm>
</role>
</name>
<typeOfResource>text</typeOfResource>
<genre>info:eu-repo/semantics/article/</genre>
<originInfo>
<dateIssued encoding="iso8601">1987</dateIssued>
</originInfo>
<language>
<languageTerm authority="rfc3066" type="code">en</languageTerm>
</language>
<abstract>In an open field spontaneously hypertensive rats (SHR) exhibited lower scores for grooming when compared to their normotensive controls, the Wistar Kyoto rats (WKY). After i.c.v. injection of 1 µg ACTH1--24 cumulative 50-min grooming scores were lower in SHR. Analysis of subscores indicated that the lesser effect of ACTH in SHR was especially prominent for headwashing and anogenital grooming. Moreover, a time course study revealed that the difference between SHR and WKY occurred in the first 6 observation periods of 5 min and thereafter disappeared. The results are discussed in the light of behavioral and central neurochemical differences between SHR and WKY.
</abstract>
<subject>
<topic>grooming</topic>
<topic>hypertension</topic>
</subject>
<classification>Farmacie</classification>
<relatedItem type="host">
<identifier type="uri">URN:ISSN:0304-3940</identifier>
<titleInfo>
<title>Neuroscience Letter</title>
</titleInfo>
<part>
<detail type="volume">
<number>77</number>
</detail>
<detail type="issue">
<number>1</number>
</detail>
<extent unit="page">
<start>71</start>
<end>75</end>
</extent>
</part>
</relatedItem>
<identifier type="uri">info:doi/10.1016/0304-3940(87)90609-4</identifier>
</mods>
...
<?xml version="1.0" encoding="UTF-8"?>
<mods
version="3.2"
xmlns="http://www.loc.gov/mods/v3"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.loc.gov/mods/v3
http://www.loc.gov/standards/mods/v3/mods-3-2.xsd">
<titleInfo>
<title>Accounting information for changing business needs</title>
<subTitle>concepts of business logistics applied to treasury management decisions</subTitle>
</titleInfo>
<name type="personal" ID="A1">
<namePart type="given">Piet Erik Adolf</namePart>
<namePart type="family">Vandenbossche</namePart>
<role>
<roleTerm authority="marcrelator" type="code">aut</roleTerm>
</role>
<affiliation>
Rijksuniversiteit Groningen. Faculteit Bedrijfskunde.
SOM Research School
</affiliation>
</name>
<extension>
<daiList
xmlns:dai="info:eu-repo/dai"
xsi:schemaLocation="info:eu-repo/dai http://www.surfgroepen.nl/sites/oai/metadata/Shared%20Documents/dai extension.xsd">
<identifier
IDref="A1"
authority="info:eu-repo/dai/nl">157455599</identifier>
</daiList>
</extension>
<name type="personal">
<namePart type="family">Wortmann</namePart>
<namePart type="given">J.C.</namePart>
<role>
<!-- promotor ->
<roleTerm authority="marcrelator" type="code">ths</roleTerm>
</role>
<affiliation>
Rijksuniversiteit Groningen.
Faculteit Bedrijfskunde
</affiliation>
</name>
<name type="personal">
<namePart>Meer-Kooistra, J. van der</namePart>
<role>
<roleTerm authority="marcrelator" type="code">ths</roleTerm>
</role>
<affiliation>
Rijksuniversiteit Groningen.
Faculteit Bedrijfskunde
</affiliation>
</name>
<name type="corporate">
<namePart>Rijksuniversiteit Groningen</namePart>
<role>
<roleTerm authority="marcrelator" type="code">dgg</roleTerm>
</role>
</name>
<typeOfResource>text</typeOfResource>
<genre>info:eu-repo/semantics/doctoralThesis<genre>
<originInfo>
<place>
<placeTerm type="text">Groningen</placeTerm>
</place>
<publisher>Rijksuniversiteit Groningen</publisher>
<dateIssued encoding="iso8601">2005</dateIssued>
</originInfo>
<language>
<languageTerm authority="rfc3066" type="code">en</languageTerm>
</language>
<physicalDescription>
<extent>322 p.</extent>
</physicalDescription>
<abstract>This work is about the transfer and contextual constitution of organisational forms (specifically of production systems) in the subsidiaries of multinational enterprises (MNEs). The work suggests that subsidiaries are simultaneously embedded in a host country and parent company context as well as in a strategic and institutional context. It is argued that only if we consider strategic choices at the corporate and subsidiary level as well as the institutional and strategic context can we understand the contextual constitution of subsidiary production systems in MNEs. Empirically the work asks how and why the contextual constitution – - i.e. the hybridization profile – - of four MNE automobile subsidiaries in India differs.
</abstract>
<subject authority="info:eu-repo/authority/goo">
<topic>Internationale ondernemingen</topic>
<topic>Hybride organisaties</topic>
<topic>Personeelsmanagement</topic>
<topic>Productiemanagement</topic>
<genre>Proefschriften (vorm)</genre>
</subject>
</mods>
...
== there are two examples of patents one from NL and one from the US. Apart from this difference in countries, it is unclear what the other differences are. Better to have an example of a patent and a patent application? An expert on patents must review this. ==
<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns="http://www.loc.gov/mods/v3"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.loc.gov/mods/v3
http://www.loc.gov/standards/mods/v3/mods-3-2.xsd">
<titleInfo xml:lang="nl">
<title>
Inrichting en werkwijze voor de scheiding van mengsels van chemische
substanties
</title>
</titleInfo>
<name type="personal" ID="n1">
<namePart type="given">Jan Cornelis</namePart>
<namePart type="family">Hummelen</namePart>
<role>
<roleTerm authority="marcrelator" type="code">pth</roleTerm>
<!---- pth = patent holder ->
</role>
</name>
<!-- DAI ->
<extension>
<daiList
xmlns:dai="info:eu-repo/dai"
xsi:schemaLocation="info:eu-repo/dai http://www.surfgroepen.nl/sites/oai/metadata/Shared%20Documents/dai extension.xsd">
<identifier
IDref="n1"
authority="info:eu-repo/dai/nl">070951144</identifier>
</daiList>
</extension>
<typeOfResource>text</typeOfResource>
<genre>info:eu-repo/semantics/patent</genre>
<identifier type="octrooiraad">9200341</identifier>
===== Not according to these guidelines !!
<!-- type van identifier is naam van uitgevende instantie ->
<!--
# country code of the filing country
# publication number
# filing number
# kind of document
# filing date
# publication date
# applicant
# inventor
# International Patent Classification (IPC)
# title
# priorities
# abstract (searchable fulltext)
# claims (searchable fulltext)
# description (searchable fulltext)
# Inpadoc legal status data (oppositions, cancellations...)
-->
<originInfo>
<place>
<placeTerm authority="marccountry" type="code">nl</placeTerm>
</place>
<publisher>Octrooiraad</publisher>
<!-- verplicht veld, maar uitgever staat niet in publicatie vermeld ->
<dateIssued encoding="iso8601">1992</dateIssued>
</originInfo>
<language>
<languageTerm authority="rfc3066" type="code">nl</languageTerm>
</language>
<physicalDescription>
<extent>10 p.</extent>
</physicalDescription>
</mods>
...
<?xml version="1.0" encoding="UTF-8"?>
<mods
version="3.2"
xmlns="http://www.loc.gov/mods/v3"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.loc.gov/mods/v3
http://www.loc.gov/standards/mods/v3/mods-3-2.xsd">
<titleInfo>
<title>Optical limiting materials</title>
</titleInfo>
<name type="personal" ID="n1">
<namePart type="family">McBranch</namePart>
<namePart type="given">Duncan W.</namePart>
<role>
<roleTerm authority="marcrelator" type="code">pth</roleTerm>
</role>
</name>
<name type="personal" ID="n2">
<namePart type="family">Mattes</namePart>
<namePart type="given">Benjamin R.</namePart>
<role>
<roleTerm authority="marcrelator" type="code">pth</roleTerm>
</role>
</name>
<name type="personal" ID="n3">
<namePart type="family">Koskelo</namePart>
<namePart type="given">Aaron C.</namePart>
<role>
<roleTerm authority="marcrelator" type="code">pth</roleTerm>
</role>
</name>
<name type="personal" ID="n4">
<namePart type="family">Heeger</namePart>
<namePart type="given">Alan J.</namePart>
<role>
<roleTerm authority="marcrelator" type="code">pth</roleTerm>
</role>
</name>
<name type="personal" ID="n5">
<namePart type="family">Robinson</namePart>
<namePart type="given">Jeanne M.</namePart>
<role>
<roleTerm authority="marcrelator" type="code">pth</roleTerm>
</role>
</name>
<name type="personal" ID="n6">
<namePart type="family">Smilowitz</namePart>
<namePart type="given">Laura B.</namePart>
<role>
<roleTerm authority="marcrelator" type="code">pth</roleTerm>
</role>
</name>
<name type="personal" ID="n7">
<namePart type="family">Klimov</namePart>
<namePart type="given">Victor L.</namePart>
<role>
<roleTerm authority="marcrelator" type="code">pth</roleTerm>
</role>
</name>
<name type="personal" ID="n8">
<namePart type="family">Cha</namePart>
<namePart type="given">Myoungsik</namePart>
<role>
<roleTerm authority="marcrelator" type="code">pth</roleTerm>
</role>
</name>
<name type="personal" ID="n9">
<namePart type="family">Serdar Sarifici</namePart>
<namePart type="given">N.</namePart>
<role>
<roleTerm authority="marcrelator" type="code">pth</roleTerm>
</role>
</name>
<name type="personal" ID="n10">
<namePart type="family">Hummelen</namePart>
<namePart type="given">Jan C.</namePart>
<role>
<roleTerm authority="marcrelator" type="code">pth</roleTerm>
</role>
</name>
<!-- DAI ->
<extension>
<daiList
xmlns:dai="info:eu-repo/dai"
xsi:schemaLocation="info:eu-repo/dai
http://www.surfgroepen.nl/sites/oai/metadata/Shared%20Documents/dai-extension.xsd">
<identifier
IDref="n10" authority="info:eu-repo/dai/n1">070951144</identifier>
</daiList>
</extension>
<typeOfResource>text</typeOfResource>
<genre>info:eu-repo/semantics/patent</genre>
<identifier type="United States patent">5,741,442</identifier>
== this is not according to these guidelines !
<!-- type van identifier is naam van uitgevende instantie -->
<originInfo>
<place>
<placeTerm authority="marccountry" type="code">us</placeTerm>
</place>
<publisher>United States Patent ???</publisher>
<!-- verplicht veld, maar uitgever staat niet in publicatie vermeld -->
<dateIssued encoding="iso8601">1998</dateIssued>
<
</originInfo>
<language>
<languageTerm authority="rfc3066" type="code">en</languageTerm>
</language>
<physicalDescription>
<extent>11 p.</extent>
</physicalDescription>
<recordInfo>
<recordCreationDate encoding="iso8601">2007-06-29</recordCreationDate>
<recordChangeDate encoding="iso8601">2007-11-19</recordChangeDate>
<recordIdentifier>4357afd8d5b13</recordIdentifier>
</recordInfo>
</mods>
...
== this is also an example of how to refer to another version; in this case the other version has other co-authors; which identifiier has to be used for referring to the other version? ==
<?xml version="1.0" encoding="UTF-8" ?>
<!-- file: ModsUMWorkingPaper.xml ->
<mods
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.loc.gov/mods/v3"
xsi:schemaLocation="http://www.loc.gov/mods/v3
http://www.loc.gov/standards/mods/v3/mods-3-2.xsd">
<titleInfo>
<title>Good and bad objects</title>
<subTitle>cardinality-based rules</subTitle>
</titleInfo>
<name type="personal">
<namePart type="given">D.A.</namePart>
<namePart type="family">Dimitrov</namePart>
<role>
<roleTerm authority="marcrelator" type="code">aut</roleTerm>
</role>
<affiliation>Universiteit van Tilburg</affiliation>
</name>
<name type="personal" ID="n1">
<namePart type="given">P.E.M.</namePart>
<namePart type="family">Borm</namePart>
<role>
<roleTerm authority="marcrelator" type="code">aut</roleTerm>
</role>
<affiliation>Universiteit van Tilburg</affiliation>
</name>
<name type="personal" ID="n2">
<namePart type="given">R.L.P.</namePart>
<namePart type="family">Hendrickx</namePart>
<role>
<roleTerm authority="marcrelator" type="code">aut</roleTerm>
</role>
<affiliation>Universiteit van Tilburg</affiliation>
</name>
<extension>
<daiList
xmlns:dai="http://eu-repo/dai"
xsi:schemaLocation="http://eu-repo/dai http://www.surfgroepen.nl/sites/oai/metadata/Shared%20Documents/dai extension.xsd">
<identifier
IDref="n1"
authority="info:eu-repo/dai/nl">075062763</identifier>
<identifier
IDref="n1"
authority="info:eu-repo/dai/nl">254984509</identifier>
</daiList>
</extension>
<typeOfResource>text</typeOfResource>
<genre>info:eu-repo/semantics/workingPaper</genre>
<originInfo>
<dateIssued encoding="iso8601">2003</dateIssued>
</originInfo>
<language>
<languageTerm authority="rfc3066" type="code">en</languageTerm>
</language>
<physicalDescription>
<extent>14 pages</extent>
</physicalDescription>
<abstract xml:lang="en">
We consider the problem of ranking sets of objects, the members of which are mutually compatible. Assuming that each object is either good or bad, we axiomatically characterize three cardinality-based rules which arise naturally in this dichotomous setting. They are what we call the symmetric di.erence rule, the lexicographic good-bad rule, and the lexicographic bad-good rule. Each of these rules induces a unique additive separable preference relation over the set of all groups of objects.
</abstract>
<subject xml:lang="en" authority="local">
<topic>welfare economics</topic>
</subject>
<classification
authority="info:eurepo/authority/jel">D63</classification>
<classification
authority="info:eurepo/authority/jel">D71</classification>
<relatedItem type="series">
<titleInfo>
<title>Discussion Paper</title>
</titleInfo>
<identifier type="issn">0924-7815</identifier>
<originInfo>
<publisher>
Tilburg University. Center for Economic Research
</publisher>
</originInfo>
<part>
<detail type="volume">
<number>2003-49</number>
</detail>
</part>
</relatedItem>
<!- add co-authors; in this case they differ from the working paper !!->
<relatedItem type="succeeding">
<titleInfo>
<title>Good and bad objects</title>
<subTitle>the symmetric difference rule</subTitle>
</titleInfo>
<relatedItem type="host">
<titleInfo>
<title>Economics bulletin</title>
</titleInfo>
<part>
<detail type="volume">
<number>4</number>
</detail>
<detail type="issue">
<number>11</number>
</detail>
<extent unit="page">
<start>1</start>
<end>7</end>
</extent>
<date>2004</date>
</part>
</relatedItem>
</relatedItem>
</mods>