
<mods xmlns="http://www.loc.gov/mods/v3" xmlns:xlink="http://www.w3.org/1999/xlink" 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-4.xsd">
    
    <titleInfo>
        <title>Money for Nothing and Privacy for Free?</title>
    </titleInfo>
    <name type="personal" ID="sks2142">
        <namePart type="family">Sheth</namePart>
        <namePart type="given">Swapneel Kalpesh</namePart>
        <role>
            <roleTerm type="text">author</roleTerm>
        </role>
        <affiliation>Columbia University. Computer Science</affiliation>
    </name>
    <name type="personal" ID="tm2118">
        <namePart type="family">Malkin</namePart>
        <namePart type="given">Tal G.</namePart>
        <role>
            <roleTerm type="text">author</roleTerm>
        </role>
        <affiliation>Columbia University. Computer Science</affiliation>
    </name>
    <name type="personal" ID="gek1">
        <namePart type="family">Kaiser</namePart>
        <namePart type="given">Gail E.</namePart>
        <role>
            <roleTerm type="text">author</roleTerm>
        </role>
        <affiliation>Columbia University. Computer Science</affiliation>
    </name>
    <name type="corporate">
        <namePart>Columbia University. Computer Science</namePart>
        <role>
            <roleTerm type="text">originator</roleTerm>
        </role>
        <role>
            <roleTerm type="text">contributor</roleTerm>
        </role>
    </name>
    <typeOfResource>text</typeOfResource>
    <genre>Technical reports</genre>
    
    <originInfo>
        <place>
            <placeTerm type="text">New York</placeTerm>
        </place>
        <publisher>Department of Computer Science, Columbia University</publisher>
        <dateIssued encoding="w3cdtf" keyDate="yes">2011</dateIssued>
    </originInfo>
    <abstract>Privacy in the context of ubiquitous social computing systems has become a major concern for the society at large. As the number of online social computing systems that collect user data grows, this privacy threat is further exacerbated. There has been some work (both, recent and older) on addressing these privacy concerns. These approaches typically require extra computational resources, which might be beneficial where privacy is concerned, but when dealing with Green Computing and sustainability, this is not a great option. Spending more computation time results in spending more energy and more resources that make the software system less sustainable. Ideally, what we would like are techniques for designing software systems that address these privacy concerns but which are also sustainable - systems where privacy could be achieved &quot;for free,&quot; i.e., without having to spend extra computational effort. In this paper, we describe how privacy can be achieved for free - an accidental and beneficial side effect of doing some existing computation - and what types of privacy threats it can mitigate. More precisely, we describe a &quot;Privacy for Free&quot; design pattern and show its feasibility, sustainability, and utility in building complex social computing systems.</abstract>
    <subject>
        <topic>Computer science</topic>
    </subject>
    <relatedItem type="series" ID="r.1">
        <titleInfo>
            <title>Columbia University Computer Science Technical Reports</title>
            <partNumber>CUCS-043-11</partNumber>
        </titleInfo>
    </relatedItem>
    <identifier type="hdl">http://hdl.handle.net/10022/AC:P:11490</identifier>

    <language>
        <languageTerm type="text">English</languageTerm>
    </language>
    
    <location>
        <physicalLocation authority="marcorg">NNC</physicalLocation>
    </location>
    
    <recordInfo>
        <recordContentSource authority="marcorg">NNC</recordContentSource>
        <recordCreationDate encoding="w3cdtf">2011-10-19 10:36:31 -0400</recordCreationDate>
        <recordChangeDate encoding="w3cdtf">2011-10-19 11:26:05 -0400</recordChangeDate>
        <recordIdentifier>5473</recordIdentifier>
        <languageOfCataloging>
            <languageTerm authority="iso639-2b">eng</languageTerm>
        </languageOfCataloging>
    </recordInfo>
    
</mods>
