<?xml version="1.0" encoding="UTF-8"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-07-20T05:38:58Z</responseDate>
  <request identifier="6103" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:6103</identifier>
        <datestamp>2024-03-06T10:37:59Z</datestamp>
        <setSpec>ddc:004</setSpec>
        <setSpec>open_access</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>LJGS: Gradual Security Types for Object-Oriented Languages</dc:title>
          <dc:creator>Fennell, Luminous</dc:creator>
          <dc:creator>Thiemann, Peter</dc:creator>
          <dc:subject>gradual typing</dc:subject>
          <dc:subject>security typing</dc:subject>
          <dc:subject>Java</dc:subject>
          <dc:subject>hybrid information flow control</dc:subject>
          <dc:description>LJGS is a lightweight Java core calculus with a gradual security type system. The calculus guarantees secure information flow for&#13;
sequential, class-based, typed object-oriented programming with&#13;
mutable objects and virtual method calls. An LJGS program is&#13;
composed of fragments that are checked either statically or&#13;
dynamically. Statically checked fragments adhere to a security type&#13;
system so that they incur no run-time penalty whereas dynamically&#13;
checked fragments rely on run-time security labels. The programmer&#13;
marks the boundaries between static and dynamic checking with casts&#13;
so that it is always clear whether a program fragment requires&#13;
run-time checks. LJGS requires security annotations on fields and&#13;
methods. A field annotation either specifies a fixed static&#13;
security level or it prescribes dynamic checking. A method&#13;
annotation specifies a constrained polymorphic security signature.&#13;
The types of local variables in method bodies are analyzed&#13;
flow-sensitively and require no annotation. The dynamic checking of&#13;
fields relies on a static points-to analysis to approximate implicit&#13;
flows. We prove type soundness and non-interference for LJGS.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Luminous Fennell and Peter Thiemann</dc:contributor>
          <dc:date>2016</dc:date>
          <dc:relation>Is Part Of LIPIcs, Volume 56, 30th European Conference on Object-Oriented Programming (ECOOP 2016)</dc:relation>
          <dc:type>InProceedings</dc:type>
          <dc:type>Text</dc:type>
          <dc:type>doc-type:ResearchArticle</dc:type>
          <dc:type>publishedVersion</dc:type>
          <dc:format>application/pdf</dc:format>
          <dc:identifier>doi:10.4230/LIPIcs.ECOOP.2016.9</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-61031</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/LIPIcs.ECOOP.2016.9</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by/3.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
