publishing/WP.html

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="utf-8">
    <title>Core Techonologies for Web Publications</title>
</head>
<body>
    <header>
        <h1>Core Techonologies for Web Publications</h1>
    </header>
    <main>
        <section class="featureset well-deployed">
            <h2>Well-deployed and/or fully specified technologies</h2>
            <ul>
                <li data-feature="Publishing and Linking"><a data-featureid="publishing-linking">Publishing and Linking</a>: provides the definition of a number of common terms (“address”, “client”, etc.) that Web Publications rely on.</li>

                <li><span data-feature="Selectors and States"><a data-featureid="selectors-states">Selectors and States</a></span> may provide the basis for a possible replacement of <a href="http://www.idpf.org/epub/linking/cfi/epub-cfi-20111011.html">EPUBCFI</a>, i.e., providing a richer way to address and select portions of (HTML) content. Note that this work is based on the <span data-feature="Web Annotation Model"><a data-featureid="annotation-model">Web Annotation Model</a></span> Recommendation.</li>

                <li data-feature="Browing Contexts">
                    The lifecyle of a WP may depend on, or rely on, features defined through the concept of <a data-featureid="html5-browsing-context">Browsing Contexts</a>.
                </li>

                <li data-feature="Subresource Integrity">
                    <a data-featureid="sri">Subresource Integrity</a> may be used when controlling and adding information concerning the integrity of a full Web Publication.
                </li>
            </ul>
        </section>
        <section class="featureset in-progress">
            <h2>Specifications in progress</h2>
            <ul>
                <li data-feature="Web Application Manifest"><a data-featureid="appmanifest">Web Application Manifest</a> could serve as the basis for the serialization of <a href="https://w3c.github.io/wpub/#infoset">Web Publications Informations Sets</a>.</li>

                <li data-feature="Resource Hints">Web Publications may contain a large number of resources; as an optimization step user agents may rely on various prefetch strategies to load those content if the right information is provided by the Web Publication itself. Such optimizations may rely on the <a data-featureid="resource-hints">Resource Hints</a> specification.</li>

                <li data-feature="HTML Extensions">User Agents for Web Publications may have to propose some extensions to HTML (e.g., additional attributes for accessibility). The <a data-featureid="html-extensions">HTML Extension Specifications</a> provides a good starting point for the roadmap to such extensions.</li>

                <li data-feature="Service Workers"><a data-featureid="serviceworkers">Service Workers</a> may become the basis for the implementation of Browser based Web Publication User agents in providing offline use.</li>
                
                <li data-feature="Content Security Policy">
                    <a data-featureid="csp3">Content Security Policy</a> is another resource that may be used when controlling and adding information concerning the integrity of a full Web Publication.
                </li>
            </ul>
        </section>
    </main>
<script src="../js/generate.js"></script>
</body>
</html>