docs/index.html

<!DOCTYPE html>
<html lang="en">
  <head>
    <title>pathogen Vocabulary v0.0</title>
    <meta http-equiv=" Content-Type" content="text/html;charset=utf-8" />

    <script
      src="https://www.w3.org/Tools/respec/respec-w3c"
      class="remove"
    ></script>
    <script type="text/javascript" class="remove">
      var respecConfig = {
        // specification status (e.g., WD, LCWD, NOTE, etc.). If in doubt use ED.
        specStatus: 'UNOFFICIAL',

        // the specification's short name, as in http://www.w3.org/TR/short-name/
        shortName: 'pathogen-vocab',

        // if you wish the publication date to be other than today, set this
        // publishDate:  "2009-08-06",

        // if there is a previously published draft,
        // uncomment this and set its YYYY-MM-DD date
        // and its maturity status
        previousPublishDate: '2020-09-30',
        previousMaturity: 'UNOFFICIAL',

        // if there a publicly available Editor's Draft, this is the link
        edDraftURI: 'https://w3c-ccg.github.io/pathogen-vocab',

        // if this is a LCWD, uncomment and set the end of its review period
        // lcEnd: "2009-08-05",

        // if you want to have extra CSS, append them to this list
        // it is recommended that the respec.css stylesheet be kept
        //extraCSS:             ["spec.css", "prettify.css"],

        // editors, add as many as you like
        // only "name" is required
        editors: [
          {
            name: 'xxx',
            url: 'xxx',
            company: 'xxx',
            companyURL: 'xxx',
          },
          
        ],

        // extend the bibliography entries
        //localBiblio: webpayments.localBiblio,
        // group: "w3c-ccg",
        // {
        //   name: "Credentials Community Group",
        //   url: "https://www.w3.org/community/credentials/",
        //   list: "public-credentials",
        //   patentUri: "https://www.w3.org/community/about/agreements/cla/",
        // }
        // wg: respecPagesJson.group.name,
        // // URI of the public WG page
        // wgURI: respecPagesJson.group.url,
        // // name (with the @w3c.org) of the public mailing to which comments are due
        // wgPublicList: respecPagesJson.group.list,
        // URI of the patent status for this WG, for Rec-track documents
        // !!!! IMPORTANT !!!!
        // This is important for Rec-track documents, do not copy a patent URI from a random
        // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
        // Team Contact.
        // wgPatentURI: respecPagesJson.group.patentUri,

        otherLinks: [
          {
            key: 'Source Control',
            data: [
              {
                value: 'https://github.com/w3c-ccg/pathogen-vocab',
                href: 'https://github.com/w3c-ccg/pathogen-vocab',
              },
            ],
          },
          {
            key: 'Issue Tracker',
            data: [
              {
                value: 'https://github.com/w3c-ccg/pathogen-vocab/issues',
                href: 'https://github.com/w3c-ccg/pathogen-vocab/issues',
              },
            ],
          },
        ],

        // URI of the patent status for this WG, for Rec-track documents
        // !!!! IMPORTANT !!!!
        // This is important for Rec-track documents, do not copy a patent URI from a random
        // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
        // Team Contact.
        // wgPatentURI:  "",
        maxTocLevel: 2,
        /*preProcess: [ webpayments.preProcess ],
      alternateFormats: [ {uri: "diff-20111214.html", label: "diff to previous version"} ],
      */
        localBiblio: {
          'RDF-DATASET-NORMALIZATION': {
            title: 'RDF Dataset Normalization 1.0',
            href: 'http://json-ld.github.io/normalization/spec/',
            authors: ['David Longley', 'Manu Sporny'],
            status: 'CGDRAFT',
            publisher: 'JSON-LD Community Group',
          },
        },
      };
    </script>
    <style>
      table {
        width: 100%;
      }
    </style>
  </head>

  <body>
    <section
      data-include="sections/abstract.html"
      data-include-replace="true"
    ></section>

    <section id="sotd">
      <p>
        This repository will be versioned at periodic points in time with a Q1
        Calendar Year target for major releases. Versioning tags will follow a
        pattern of `[MAJOR].[MINOR].[PATCH]`
        <br /><br />
        Version Definitions:
      </p>
      <ul>
        <li>
          MAJOR - significant changes rolled forward from the previous major
          version. Major versions MAY include breaking or non-backwards
          compatible changes
        </li>
        <li>
          MINOR - backwards compatible changes that may introduce new
          functionality or extensions of objects that are backwards compatible
        </li>
        <li>
          PATCH - minor changes that are non breaking and resolve discovered
          issues or bugs
        </li>
      </ul>
      As a rule, versioning will follow the specification outlined in the
      <a href="https://semver.org/">Semantic Versioning 2.0</a> spec This
      approach to versioning gives the ability to integrate with and provided
      automated testing and validation against defined types without worry of
      instability or breaking changes being introduced, while also limiting the
      frequency of possibly breaking changes to prevent a large number of
      incompatible versions.
      <p></p>

      <p>
        To contribue to this vocabulary or reference technical details related
        to the project, please reference the primary README located on
        <a href="https://github.com/w3c-ccg/pathogen-vocab/">github</a>
      </p>

      <p>
        Please
        <a href="https://github.com/w3c-ccg/pathogen-vocab/issues/"
          >open an issue</a
        >
        , if you wish to collaborate on this specification.
      </p>

      <p>
        You may also reach out via the mailing list:
        <a href="mailto:public-credentials@w3.org">public-credentials@w3.org</a>
        (<a href="mailto:public-credentials-request@w3.org?subject=subscribe"
          >subscribe</a
        >,
        <a href="https://lists.w3.org/Archives/Public/public-credentials/"
          >archives</a
        >)
      </p>
    </section>

    <section class="informative">
      <h2>Introduction</h2>

      <p>
        This specification describes a Linked Data vocabulary for asserting
        Verifiable Credentials related to pathogen information, such as
        chemical properties, mechanical properties, country of origin, and other
        attributes used to determine the status of a products and materials in a
        supply chain.
      </p>

      <p>
        Generally, this vocabulary may be looked at as a set of common objects 
        that are shared across multiple business verticals, and vertical or
        use case specific items that apply to one or more specific commodities
        or market segments. A primary goal of this specification is to 
        standardize the creation of Verifiable Credentials from standardized
        JSON-LD which is itself created from JSON Schema definitions as would
        normally be passed of REST and other APIs.  This promotes code re-use
        and establishes a pattern for the creation of JSON-LD and related
        Verifiable Credentials derived from those JSON-LD objects in a manner
        that is friendly to code and API development as well as to promote
        better interoperability between vendors who serve common or related
        markets.
      </p>

      <p>
        The <a href="#vocabulary">Vocabulary</a> section covers each vocabulary
        item, its properties, other attributes, and provides and example 
        Verifiable Credential for each item.
      </p>

      <p>
        This repository has primary contributors from four main market segments,
        and has subject matter experts from those market segments delegated
        as leads for objects related to vocabulary items for each segment.  
        <br />
        These subject matter leads help identify common elements across verticals
        as well as in assessing contributions of new objects to the vocabulary. 
        <br />
        <table>
          <thead>
            <tr>
              <td>Market Segment</td>
              <td>Subject Matter Expert</td>
              <td>Contact</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>xxx</td>
              <td>xxx</td>
              <td>xxx</td>
            </tr>
          </tbody>
        </table>
      </p>

      <section class="informative">
        <h3>Use Cases and Requirements</h3>

        <p>
          The following use cases outline a number of key scenarios that readers
          might find useful in a variety of sectors, especially those that deal
          with cross border supply chain data interchange.
        </p>

        <!-- definition styling works well for these, but we can adjust at a later data should we want to break out into another format -->
        <section>
          <h5>Covid19 Test Passes</h5>
          <dl class="termlist">
            <p>
              xxxx
            </p>

            <p>
              Axxxx
            </p>

          
          </dl>
        
      </section>
    </section>

    <section id="terminology" class="informative">
      <h2>Terminology</h2>
      <p>
        The following terms are used to describe concepts in this specification.
      </p>

      <dl class="termlist">
        <dt><dfn data-lt="entities|entity's">entity</dfn></dt>
        <dd>
          A thing with distinct and independent existence, such as a person,
          organization, or device that performs one or more roles in the
          ecosystem.
        </dd>
        <dt><dfn>user agent</dfn></dt>
        <dd>
          A program, such as a browser or other Web client, that mediates the
          communication between the various roles in this specification.
        </dd>
        <dt><dfn data-lt="URI|URIs">URI</dfn></dt>
        <dd>An identifier as defined by [[RFC3986]].</dd>
      </dl>
    </section>

    <section
      data-include="sections/vocab.html"
      data-include-replace="true"
    ></section>

    <section id="conformance"></section>

    <section class="informative">
      <h2>Privacy Considerations</h2>

      <p>
        This section details the general privacy considerations and specific
        privacy implications of deploying this specification into production
        environments.
      </p>
    </section>

    <section class="informative">
      <h2>Security Considerations</h2>

      <p>
        There are a number of security considerations that implementers should
        be aware of when processing data described by this specification.
        Ignoring or not understanding the implications of this section can
        result in security vulnerabilities.
      </p>

      <p>
        While this section attempts to highlight a broad set of security
        considerations, it is not a complete list. Implementers are urged to
        seek the advice of security and cryptography professionals when
        implementing mission critical systems using the technology outlined in
        this specification.
      </p>
    </section>

    <section class="informative">
      <h2>Accessibility Considerations</h2>

      <p>
        There are a number of accessibility considerations implementers should
        be aware of when processing data described in this specification. As
        with any web standards or protocols implementation, ignoring
        accessibility issues makes this information unusable to a large subset
        of the population. It is important to follow accessibility guidelines
        and standards, such as [[WCAG21]], to ensure all people, regardless of
        ability, can make use of this data. This is especially important when
        establishing systems utilizing cryptography, which have historically
        created problems for assistive technologies.
      </p>

      <p>
        This section details the general accessibility considerations to take
        into account when utilizing this data model.
      </p>
    </section>

    <section class="informative">
      <h2>Internationalization Considerations</h2>

      <p>
        There are a number of internationalization considerations implementers
        should be aware of when publishing data described in this specification.
        As with any web standards or protocols implementation, ignoring
        internationalization makes it difficult for data to be produced and
        consumed across a disparate set of languages and societies, which would
        limit the applicability of the specification and significantly diminish
        its value as a standard.
      </p>

      <p>
        This section outlines general internationalization considerations to
        take into account when utilizing this data model.
      </p>
    </section>
  </body>
</html>