dokieli documentation dokieli 文档

Is there such thing as a "dokieli" document? Must there be?

有这样的“dokieli”文档吗？肯定有吗？

Article文章

An article may contain RDF classes like schema:CreativeWork sioc:Post prov:Entity schema:Article, otherwise, there is no unique data that would indicate that it is a "dokieli" document. If the HTML+RDFa representation includes do.js and the DOM is ready, the DO: Object { C: {…}, U: {…} } will be available. 一篇文章可能包含象 schema:CreativeWork sioc:Post prov:Entity schema:Article这样的类，否则，没有独特的数据表明它是"dokieli" 文档。如果HTML+RDFa 表述包含do.js并且DOM已经准备好，则DO: Object { C: {…}, U: {…} } 将可用。

Annotation标注

An annotation has the oa:Annotation class. It is possible to know that the article was rendered by dokieli: ?s oa:renderedVia <https://dokie.li/>, and we can assume that the annotation was created by it as well. This is not strictly true since that property could have been put there by something else. Annotations represented in HTML+RDFa do not include do.js. 一个标注有一个oa:Annotation类。有可能知道文章是由 dokieli生成的: ?s oa:renderedVia <https://dokie.li/>, 并可以假设标注是由它创建的。 因为该属性可以被其它别的东西放在那儿，所以严格说也不一定正确。在HTML+RDFa表示的标注不包括do.js.

Notification通知

A notification may have one of the following classes: as:Announce, as:Like, as:Dislike, as:Relationship. Notifications represented in HTML+RDFa do not include do.js. 一个通知可能是下列类之一: as:Announce, as:Like, as:Dislike, as:Relationship. 在HTML+RDFa中表示的通知不包括do.js.

One of the goals of dokieli is not to impose arbitrary restrictions on type of nodes as well as the order they should be in HTML+RDFa. It has its own design patterns. It is an ongoing work to make dokieli as flexible as it can be on what it can consume. Ultimately, well-formed and valid HTML - along with accompanying RDFa, Turtle, JSON-LD, TriG etc - is the only requirement here. Take what you like:

dokieli 的目标之一是不对节点的类型以及在HTML+RDFa中应具有的顺序施加任意限制。它有自己的设计模式。这是正在让dokieli在使用的时候尽可能的灵活，最终, 良好的格式和有效的 HTML——连同RDFa, Turtle，JSON-LD, TriG等——仅在这里是需要的。可以采用你喜欢的形式:

Markup syntax标记语法

HTML5 Polyglot Markup is used to ensure that when content is processed or served as HTML or XHTML (text/html, application/xhtml+xml), they can generally be used in both HTML and XML ecosystems without further intervention. See also getDocument (do.js) for details on DOM normalisation. HTML5 多元标记 用于确保当内容被处理成或用作HTML工XHTML (text/html, application/xhtml+xml)时，它们通常可以在HTML和XML生态中使用，而无需进一步干预。对于DOM规范化的详细信息，参见 getDocument (do.js) 。

Identifiers标识符

Unique identifiers (@id) may be placed on any element. Identifiers are auto-generated by normalising some input eg. sections use their heading's text content as input, tables from caption. Anything of importance should have an identifier, and aimed to be included for common patterns out of the box. @id values are reused in RDFa. See also generateAttributeId (do.js) and its application in different places. 可以将唯一标识符(@id) 放在任何元素上。标识符在规范化一些输入时自动生成，例如 section使用它们的标题文本作为输入，table则取自 caption。任何重要的东西都应该有一个标识符，并且目标是将常用模式包含在里面开箱可用。 @id 值在RDFa中重用。参见 generateAttributeId (do.js) 和它在不同地方的应用。

Outline大纲

• title is used. 使用title。
• main > article (querySelector) is considered to be the location of the primary content. 我们认为main > article (querySelector) 是主内容的定位。
• h1 is typically the first element node after main > article h1 通常是main > article之后的第一个元素节点。
• There is a resource type, eg. schema:Article that can be found in main > article which is about the article. body may contain broad classes. 有一种资源类型，例如schema:Article是关于文章，可以在main > article 中找到。 body 可能包含更宽的类。

Section分节

Sectioning is declared with section and typically have a heading, eg. h2 as its first child. Subsections may appear as a child of parent section, or as a child of div (which is a child of parent section), ie. section section or section div section. The headings of subsections are enumerated eg. section h2 would have a subsection with section h3. Sections ids and heading text are used to dynamically build the table of contents. 分节是用section声明，通常有一个标题，例如 h2 作为它的第一个子元素。子节可以作为父section的子元素, 或者作为div（它是父section的子元素）的子元素）如section section 或 section div section. 子节的标题列举如下section h2 可以有个子分节section h3。分节id和标题文本用于动态生成目录。

<section>
  <h2>
  <div>
    <section>
      <h3>
      <div>
      <div>
      <aside>
<section>
  <h2>
  <section>
    <h3>

Aside侧边栏

asides can technically appear anywhere, but tend to appear as the last element node in section, eg. for related content, footnotes. If the aside is introduced to the DOM via JavaScript for like annotations, they have a similar structure to section. aside在技术上可以出现在任何地方，但往往出现在最后一个section节点的元素中，例如相关内容，脚注等。如果aside通过JavaScript作为标注引入到DOM中，它们有一个跟section相似的结构。

Division分割

divs within section are used to wrap a block of arbitrary markup and content. See also RDFa below. 在section中的div用来包装任意标记和内容。参见下面的RDFa。

Figure图例

figures typically have figcaptions for things like audio, canvas, iframe, img, object, pre, video, math. For code scripts, figure class="listing" is used, and pre for the code itself with code The listing class is intended to have a collection of figures, which could also have a unique presentation, for example with line numbers or have its caption be prefixed with Listing and counter. figure能常用figcaptions表示事物，象 audio, canvas, iframe, img, object, pre, video, math。对于代码脚本，则使用figure class="listing"，而pre 为代码本身加上code，listing类会有一个图例集合，这些数据也可以有一个独立的表示，例如使用行号或带有Listing和计数器前缀的标题。

<section>
  <h2>
  <div>
    <section>

Comparison of systems系统比较

	d1	d2	d3	m1
Foo	m	o	n	1
Bar	k	e	y	2
Baz	!	@	#	3
Table columns list the dimensions: d1, d2, d3, and the measure: m1.

Math数学

For mathematical equations figure class="equation" can be used to hint at an equation display. MathML base equation with <math xmlns="http://www.w3.org/1998/Math/MathML"> root can be included here (see also source). Alternatively, if MathJax JavaScript is available in the document, (La)TeX, eg. \lim_{x \to \infty} \exp(-x) = 0 and ASCIIMath, eg. sum_(i=1)^n i^3=((n(n+1))/2)^2, syntaxes can be input within the authoring mode (via Edit). 对数学等式figure class="equation"可以用来显示等式。基于MathML 的等式使用 <math xmlns="http://www.w3.org/1998/Math/MathML"> 根，可以包含在这里(参见源代码).，或者，如果在文档中存在 MathJax JavaScript，则可以使用 (La)TeX, 例如 \lim_{x \to \infty} \exp(-x) = 0 和 ASCIIMath, 例如 sum_(i=1)^n i^3=((n(n+1))/2)^2, 语法可以在创作模式中输入 (通过Edit)。

$\begin{array}{c}\underset{n\to \infty }{\lim }x=0\end{array}$

Turtle, JSON-LD, and TriG syntaxes are placed within respective script blocks in head eg. <script id="meta-json-ld" type="application/ld+json" title="JSON-LD"></script>. Data is enclosed in CDATA sections. This pattern is detected, visible and editable from Embed Data in dokieli menu. See also showEmbedData (do.js).Embedding Turtle, JSON-LD, and TriG嵌入Turtle, JSON-LD和TriG

Turtle, JSON-LD和TriG 语法被放置在head中相应的script块里，例如 <script id="meta-json-ld" type="application/ld+json" title="JSON-LD"></script>。数据则由CDATA节包围。如果探测到此模式，则可以在 dokieli 菜单的Embed Data中查看和编加。参见showEmbedData (do.js).

CSS

Multiple stylesheets can be included with @media, and when accompanied with @title, some user-agents can provide options for the user to switch between them, as well as from the dokieli menu, eg. 可以用@media包含多个样式表，并且当附带@title时，一些用户代理可以为用户提供它们之间的切换选项，例如在 dokieli 菜单中：

<!-- Primary stylesheet -->
<link href="media/css/basic.css" media="all" rel="stylesheet" title="Basic" />
<!-- Alternate stylesheet -->
<link href="media/css/acm.css" media="all" rel="stylesheet alternate" title="ACM" />
<!-- Applied by default-->
<link href="https://dokie.li/media/css/do.css" media="all" rel="stylesheet" />

See also showViews (do.js). 参见showViews (do.js)。

RDFa

dokieli can consume and produce RDFa Core 1.1 syntax. dokieli可以使用和生成 RDFa Core 1.1 语法。

To preserve the order of content, @inlist is used eg. <section inlist="", <dd id="Sarven-Capadisli" inlist="" rel="bibo:authorList" resource="http://csarven.ca/#i">. 为了保持内容的顺序，使用 @inlist，例如 <section inlist="", <dd id="Sarven-Capadisli" inlist="" rel="bibo:authorList" resource="http://csarven.ca/#i">.

A sections @id value is used as part of section's @resource as a fragment, eg. <section id="introduction" rel="schema:hasPart" resource="#introduction">. This allows the same identifier to be used for humans and machines, the value is derived from normalising its heading value as mentioned earlier. section的@id值用作 section的 @resource的分片，例如 <section id="introduction" rel="schema:hasPart" resource="#introduction">。这允许相同的标识符用于人和机器，该值是通过如前所述规范化其标题值而得到的。

Relating parts is done with rel="schema:hasPart", eg. sections with subsection: 关联部分通过rel="schema:hasPart"完成，例如在子节中的节：

<section id="structure-and-semantics" inlist="" rel="schema:hasPart" resource="#structure-and-semantics">
  <section id="html-patterns" inlist="" rel="schema:hasPart" resource="#html-patterns">

divs are used to hold a block of HTML markup and types of content together eg. <div datatype="rdf:HTML" property="schema:description" resource="#introduction" typeof="deo:Introduction"> makes it possible to declare that it contains HTML markup, and describes an introductory text. div用将HTML标记块和内容保存在一起，例如 <div datatype="rdf:HTML" property="schema:description" resource="#introduction" typeof="deo:Introduction">，这样可以声明它包含 HTML标记，并描述一个介绍性的文本。

Some of the prefixes (@prefix) on the body element are defined in the RDFa Core Initial Context. These prefixes are defined in dokieli for the purpose of being compact, robust, and to minimise potential errors for consumers. 在元素body上有一些前缀 (@prefix)定义在RDFa 核心初始上下文中，这些前缀在dokieli中定义，为了更加加紧凑、健壮，并最大限度的减少使用者的潜在错误。

Servers should use UTF-8 character encoding in their HTTP responses to articles, annotations, and notifications. <meta charset="utf-8" /> is used in HTML. 服务器在它们对文章、评注和通知的HTTP响应应该使用UTF-8字符编码，在HTML中使用 <meta charset="utf-8" />

<!DOCTYPE html>
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta charset="utf-8" />
    <title></title>
    <meta content="width=device-width, initial-scale=1" name="viewport" />
    <link href="https://dokie.li/media/css/basic.css" media="all" rel="stylesheet" title="Basic" />
    <link href="https://dokie.li/media/css/do.css" media="all" rel="stylesheet" />
    <link href="https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css" media="all" rel="stylesheet" />
    <script src="https://dokie.li/scripts/simplerdf.js"></script>
    <script src="https://dokie.li/scripts/medium-editor.min.js"></script>
    <script src="https://dokie.li/scripts/do.js"></script>
  </head>

  <body about="" prefix="rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# rdfs: http://www.w3.org/2000/01/rdf-schema# owl: http://www.w3.org/2002/07/owl# xsd: http://www.w3.org/2001/XMLSchema# dcterms: http://purl.org/dc/terms/ dctypes: http://purl.org/dc/dcmitype/ foaf: http://xmlns.com/foaf/0.1/ pimspace: http://www.w3.org/ns/pim/space# cc: https://creativecommons.org/ns# skos: http://www.w3.org/2004/02/skos/core# prov: http://www.w3.org/ns/prov# mem: http://mementoweb.org/ns# qb: http://purl.org/linked-data/cube# schema: http://schema.org/ void: http://rdfs.org/ns/void# rsa: http://www.w3.org/ns/auth/rsa# cert: http://www.w3.org/ns/auth/cert# wgs: http://www.w3.org/2003/01/geo/wgs84_pos# bibo: http://purl.org/ontology/bibo/ sioc: http://rdfs.org/sioc/ns# doap: http://usefulinc.com/ns/doap# dbr: http://dbpedia.org/resource/ dbp: http://dbpedia.org/property/ sio: http://semanticscience.org/resource/ opmw: http://www.opmw.org/ontology/ deo: http://purl.org/spar/deo/ doco: http://purl.org/spar/doco/ cito: http://purl.org/spar/cito/ fabio: http://purl.org/spar/fabio/ oa: http://www.w3.org/ns/oa# as: https://www.w3.org/ns/activitystreams# ldp: http://www.w3.org/ns/ldp# solid: http://www.w3.org/ns/solid/terms# acl: http://www.w3.org/ns/auth/acl# dio: https://w3id.org/dio# rel: https://www.w3.org/ns/iana/link-relations/relation#" typeof="schema:CreativeWork sioc:Post prov:Entity">
    <main>
      <article about="" typeof="schema:Article">

      </article>
    </main>
  </body>
</html>

<dl id="document-identifier">
  <dt>Identifier</dt>
  <dd><a href="http://csarven.ca/dokieli-rww" rel="owl:sameAs">http://csarven.ca/dokieli-rww</a></dd>
</dl>

<dl id="document-inbox">
  <dt>Notifications Inbox</dt>
  <dd><a href="https://linkedresearch.org/inbox/csarven.ca/dokieli-rww/" rel="ldp:inbox">inbox/</a></dd>
</dl>

<dl id="document-in-reply-to">
  <dt>In Reply To</dt>
  <dd><a href="https://linkedresearch.org/calls" rel="as:inReplyTo">Call for Linked Research</a></dd>
</dl>

<dl id="document-annotation-service">
  <dt>Annotation Service</dt>
  <dd><a href="https://linkedresearch.org/annotation/csarven.ca/dokieli-rww/" rel="oa:annotationService">annotation/</a></dd>
</dl>

<dl id="document-published">
  <dt>Published</dt>
  <dd><time content="2017-02-27T00:00:00Z" datatype="xsd:dateTime" datetime="2017-02-27T00:00:00Z" property="schema:datePublished">2017-02-27</time></dd>
</dl>

<dl id="document-modified">
  <dt>Modified</dt>
  <dd><time content="2017-03-12T00:00:00Z" datatype="xsd:dateTime" datetime="2017-03-12T00:00:00Z" property="schema:dateModified">2017-03-18</time></dd>
</dl>

<dl id="document-license">
  <dt>License</dt>
  <dd><a href="https://creativecommons.org/licenses/by/4.0/" rel="schema:license" title="Creative Commons Attribution 4.0 Unported">CC BY 4.0</a></dd>
</dl>

<dl id="document-derived-from">
  <dt>Derived From</dt<
  <dd><a href="https://dokie.li/" rel="prov:wasDerivedFrom">https://dokie.li/</a></dd>
</dl>

<dl id="document-derived-on">
  <dt>Derived On</dt>
  <dd><time datetime="2017-08-06T00:29:45.342Z">2017-08-06T00:29:45.342Z</time></dd>
</dl>

<span typeof="schema:Person">Lunatic Scholar</span>

<span about="http://csarven.ca/#i" property="schema:name">Sarven Capadisli</span>

<img alt="" height="48" rel="schema:image" src="http://csarven.ca/media/images/sarven-capadisli.jpg" width="48" />

<span about="http://csarven.ca/#i" typeof="schema:Person"><img alt="" height="48" rel="schema:image" src="http://csarven.ca/media/images/sarven-capadisli.jpg" width="48" /> <a href="http://csarven.ca/" rel="schema:url"><span about="http://csarven.ca/#i" property="schema:name">Sarven Capadisli</span></a></span>

<a about="http://csarven.ca/#i" href="http://csarven.ca/" property="schema:name" rel="schema:url" typeof="schema:Person">Sarven Capadisli</a>

<dd id="Sarven-Capadisli" inlist="" rel="bibo:authorList" resource="http://csarven.ca/#i"><span about="" rel="schema:creator schema:publisher schema:author"><!-- profile --></span></dd>

<!DOCTYPE html>
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta charset="utf-8" />
    <title>https://linkedresearch.org/annotation/csarven.ca/dokieli-rww/b6738766-3ce5-4054-96a9-ced7f05b439f</title>
  </head>
  <body>
    <main>
      <article id="b6738766-3ce5-4054-96a9-ced7f05b439f" about="i:" typeof="oa:Annotation" prefix="rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# schema: http://schema.org/ dcterms: http://purl.org/dc/terms/ oa: http://www.w3.org/ns/oa# as: https://www.w3.org/ns/activitystreams# i: https://linkedresearch.org/annotation/csarven.ca/dokieli-rww/b6738766-3ce5-4054-96a9-ced7f05b439f">
        <h1 property="schema:name">Sarven Capadisli <span rel="oa:motivatedBy" resource="oa:replying">replies</span></h1>

        <dl class="author-name">
          <dt>Authors</dt>
          <dd><span rel="schema:creator"><span about="http://csarven.ca/#i" typeof="schema:Person"><img alt="" height="48" rel="schema:image" src="http://csarven.ca/media/images/sarven-capadisli.jpg" width="48" /> <a href="http://csarven.ca/" rel="schema:url"><span about="http://csarven.ca/#i" property="schema:name">Sarven Capadisli</span></a></span></span></dd>
        </dl>

        <dl class="published">
          <dt>Published</dt>
          <dd><a href="https://linkedresearch.org/annotation/csarven.ca/dokieli-rww/b6738766-3ce5-4054-96a9-ced7f05b439f"><time datetime="2017-04-15T21:24:58.293Z" datatype="xsd:dateTime" property="schema:datePublished" content="2017-04-15T21:24:58.293Z">2017-04-15 21:24:58</time></a>
          </dd>
        </dl>

        <dl class="rights">
          <dt>Rights</dt>
          <dd><a href="https://creativecommons.org/licenses/by/4.0/" rel="dcterms:rights" title="Creative Commons Attribution">CC BY 4.0</a></dd>
        </dl>

        <dl class="canonical">
          <dt>Canonical</dt>
          <dd about="i:" rel="oa:canonical" resource="urn:uuid:48355bb0-0afd-4f73-9a18-f1e8b6fb415b">48355bb0-0afd-4f73-9a18-f1e8b6fb415b</dd>
        </dl>

        <dl class="target">
          <dt><a href="http://csarven.ca/dokieli-rww#abstract" rel="oa:hasTarget">In reply to</a> (<a about="http://csarven.ca/dokieli-rww#abstract" href="http://csarven.ca/dokieli-rww" rel="oa:hasSource" typeof="oa:SpecificResource">part of</a>)</dt>
          <dd>
            <blockquote about="http://csarven.ca/dokieli-rww#abstract" cite="http://csarven.ca/dokieli-rww#abstract">
              <div rel="oa:hasSelector" resource="i:#fragment-selector" typeof="oa:FragmentSelector">
                <dl class="conformsto">
                  <dt>Fragment selector conforms to</dt>
                  <dd><a property="rdf:value" content="abstract" xml:lang="" lang="" rel="dcterms:conformsTo" href="https://tools.ietf.org/html/rfc3987">RFC3987</a></dd>
                </dl>

                <dl class="refinedby" rel="oa:refinedBy" resource="i:#text-quote-selector" typeof="oa:TextQuoteSelector">
                  <dt>Refined by</dt>
                  <dd><span property="oa:prefix" xml:lang="en" lang="en">rchitecture and implementation, </span><mark property="oa:exact" xml:lang="en" lang="en">demonstrating advanced document authoring and interaction without a single point of control</mark><span property="oa:suffix" xml:lang="en" lang="en">. Such an environment provides t</span></dd>
                </dl>
              </div>
            </blockquote>
          </dd>
        </dl>

        <dl class="renderedvia">
          <dt>Rendered via</dt>
          <dd><a about="http://csarven.ca/dokieli-rww#abstract" href="https://dokie.li/" rel="oa:renderedVia">dokieli</a></dd>
        </dl>

        <section id="note-b6738766-3ce5-4054-96a9-ced7f05b439f" rel="oa:hasBody" resource="i:#note-b6738766-3ce5-4054-96a9-ced7f05b439f">
          <h2 property="schema:name">Note</h2>

          <dl class="rights">
            <dt>Rights</dt>
            <dd><a href="https://creativecommons.org/licenses/by/4.0/" rel="dcterms:rights" title="Creative Commons Attribution">CC BY 4.0</a></dd>
          </dl>

          <div datatype="rdf:HTML" property="rdf:value schema:description" resource="i:#note-b6738766-3ce5-4054-96a9-ced7f05b439f" typeof="oa:TextualBody">What are you trying to tell me? That I can dodge bullets?</div>
        </section>
      </article>
    </main>
  </body>
</html>

<dl class="canonical">
  <dt>Canonical</dt>
  <dd rel="oa:canonical" resource="urn:uuid:48355bb0-0afd-4f73-9a18-f1e8b6fb415b">48355bb0-0afd-4f73-9a18-f1e8b6fb415b</dd>
</dl>

<aside class="note do">
  <blockquote cite="https://linkedresearch.org/annotation/csarven.ca/dokieli-rww/b6738766-3ce5-4054-96a9-ced7f05b439f">
    <article about="i:" id="461819979" prefix="i: https://linkedresearch.org/annotation/csarven.ca/dokieli-rww/b6738766-3ce5-4054-96a9-ced7f05b439f" typeof="oa:Annotation">
    <!-- Reconstruction of the original annotation (from RDF) -->
    </article>
  </blockquote>
</aside>

<span class="ref do" rel="schema:hasPart" resource="#r-461819979" typeof="dctypes:Text"><mark id="r-461819979" property="schema:description">demonstrating advanced document authoring and interaction without a single point of control</mark><sup class="ref-annotation"><a rel="cito:hasReplyFrom" href="#461819979" resource="https://linkedresearch.org/annotation/csarven.ca/dokieli-rww/b6738766-3ce5-4054-96a9-ced7f05b439f">💬</a></sup></span>

<!DOCTYPE html>
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta charset="utf-8" />
    <title>Notification: Announced</title>
  </head>
  <body prefix="xsd: http://www.w3.org/2001/XMLSchema# rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# as: https://www.w3.org/ns/activitystreams# oa: http://www.w3.org/ns/oa# schema: http://schema.org/">
    <main>
      <article>
        <h1>Notification: Announced</h1>
        <section>
          <dl about="">
            <dt>Types</dt>
            <dd><a about="" href="https://www.w3.org/ns/activitystreams#Announce" typeof="as:Announce">Announce</a></dd>

            <dt>Object</dt>
            <dd><a href="https://linkedresearch.org/annotation/csarven.ca/dokieli-rww/b6738766-3ce5-4054-96a9-ced7f05b439f" property="as:object">https://linkedresearch.org/annotation/csarven.ca/dokieli-rww/b6738766-3ce5-4054-96a9-ced7f05b439f</a></dd>

            <dt>Target</dt>
            <dd><a href="http://csarven.ca/dokieli-rww#abstract" property="as:target">http://csarven.ca/dokieli-rww#abstract</a></dd>

            <dt>Updated</dt>
            <dd><time datetime="2017-04-15T21:31:45.711Z" datatype="xsd:dateTime" property="as:updated" content="2017-04-15T21:31:45.711Z">2017-04-15 21:31:45</time></dd>

            <dt>Actor</dt>
            <dd><a href="http://csarven.ca/#i" property="as:actor">http://csarven.ca/#i</a></dd>

            <dt>License</dt>
            <dd><a href="https://creativecommons.org/publicdomain/zero/1.0/" property="schema:license">https://creativecommons.org/publicdomain/zero/1.0/</a></dd>
          </dl>

          <dl about="https://linkedresearch.org/annotation/csarven.ca/dokieli-rww/b6738766-3ce5-4054-96a9-ced7f05b439f">
            <dt>Object type</dt>
            <dd><a about="https://linkedresearch.org/annotation/csarven.ca/dokieli-rww/b6738766-3ce5-4054-96a9-ced7f05b439f" typeof="oa:Annotation" href="http://www.w3.org/ns/oa#Annotation">Annotation</a></dd>

            <dt>Motivation</dt>
            <dd><a href="http://www.w3.org/ns/oa#replying" property="oa:motivation">replying</a></dd>
          </dl>
        </section>
      </article>
    </main>
  </body>
</html>

There UI adapts to the document mode the user is in: author, review, social. By default the social mode is engaged. The dokieli menu allows the user to engage the author mode through the Edit operation, and the review mode with Review. See also setDocumentMode (do.js).

UI适应用户所处的文档模式 : 创作, 评论, 社交l默认情况下，启用 社交模式。 dokieli 菜单 允许用户通过 编辑 操作启用创作模式，通过 评论启用评论模式。参见setDocumentMode (do.js).

Sign in登录

This is where the user can enter their WebID to let dokieli know about who they are. dokieli fetches their WebID and related information to further help with dokieli's operations. Authentication is not done at this stage. 这是用户可以输入他们的WebID以让dokieli知道他们是谁的地方。dokieli获取他们的WebID和相关信息，以进一步帮助dokieli的操作。在此阶段尚未进行身份验证。

Share分享

User can share the current article or a part of it with their contacts, automatically discovered via foaf:knows as well as traversing equivalent profiles (owl:sameAs). Notification can also be sent to specific targets by entering their IRIs. dokieli sends a notification to the selected targets with information like: who sent it, when, license, motivation. 用户可以通过其foaf:knows 自动发现的联系人共享当前文章或其中的一部分，以及遍历等效的配置文件(owl:sameAs)。通过输入IRI，也可以将通知发送到特定目标。dokieli向所选目标发送通知，其中包含以下信息：发送者，时间，许可证，动机。

Reply回复

An article can be replied with a note and have its own license. To choose the location of the reply, the resource browser can be used on personal storage or an annotation service. 可以使用笔记回复文章并拥有自己的 许可证。要选择回复的位置，资源浏览器可以用于个人存储或者一个评注服务。

Review评论

This feature changes the document mode to Review and gives different context for annotations. When a user selects a span of text, a toolbar provides the following options to motivations: 此功能将 文档模式 改为 评论并为评注提供不同的上下文。当用户选择文本范围时，工具栏会为动机提供以下选项：

Approve同意

General agreement with the selected text. Optional text should specify why it is a strong point or a convincing argument. 与所选文本达成一般性同意。可选文本用来指明为什么同意它或一个令人信服的论点。

Disapprove不同意

General disagreement with the selected text. Optional text should specify why it is a weak point, an error, or inaccurate. 与所选文本达成一般性不同意。可选文本用来指明为什么不同意，错误或不精确的地方。

Specificity特异性

Request to increase specificity on selected text. Optional text should indicate that a citation or more specificity is needed. 要求增加对所选文本的特异性。可选文本应表明需要引用或需要更多的特异性。

New新建

This feature allows a new document to be created at specified location. The new document is constructed based on If the user is signed in with their WebID and their personal storage location is identifier, the default location for the new resource will have the storage URL (pim:storage) as its base. If the user does not have a WebID and a storage, and if the article refers to an annotation service (oa:annotationService), it will use that URL instead. The URL can be input directly, and otherwise a name will be autogenerated for the resource. This feature uses the resource browser to navigate HTTP URLs. See also generateAttributeId (do.js). On create, the resulting hyperlink will be shown and a new tab in the browser will be prompted. 此功能允许在指定位置创建新文档。新文档的构建基于（如果用户使用其WebID登录并且标注了其个人存储位置），则新资源的默认位置将以存储URL(pim:storage)为基础。如果用户没有WebID和存储，并且文章引用了标注服务(oa:annotationService)，则使用它的URL。可以直接输入URL，否则将为资源自动生成名称。此功能使用 资源浏览器导航HTTP URL。另请参见generateAttributeId (do.js)。 在创建时，将显示生成的超链接，并将在浏览器中提示新的选项卡。

Open打开

Documents can be opened from a local filesystem or by entering an HTTP URL. Both options read the resource's content, and if dokieli's CSS and JavaScript are not present, they are included before updating the DOM and initiating dokieli. This feature uses the resource browser to navigate HTTP URLs. See also openDocument (do.js). 可以从本地文件系统或输入HTTP URL打开文档。这两个选项都读取了资源的内容，如果没有dokieli的CSS和JavaScript，则在更新DOM和启动dokieli之前会包含它们。此功能使用资源浏览器导航HTTP URL。另请参见openDocument（do.js）。

Save保存

This feature makes a write operation (HTTP PUT) request to the current location of the document (window.location). The document is normalised in that dokieli related items are removed from the DOM before making the request. 此功能对文档的当前位置(window.location)进行写操作(HTTP PUT)请求。因为在发出请求之前，dokieli相关项目将从DOM中删除，所以该文档是规范化的。<

Save As另存为

The Save As operation is similar to New for normalising some of the URLs and same as Save operation for normalising the DOM before making the request to specified location. If Derivation data is checked for inclusion, derived from and on information is included in the created document. This feature uses the resource browser to navigate HTTP URLs. 另存为 操作用于规范化某些URL，类似于 新建，用于在向指定位置发出请求之前规范化DOM，则与“ 保存”操作相同。如果检查是否包含派生数据，则从创建的文档中包含派生和被派生的信息。该功能使用资源浏览器导航HTTP URL。

Export导出

Provides options to 1) exports the article as HTML and save to filesystem, 2) Makes a request to the Internet Archive to crawl all resources references in this article. 提供以下选项：1）将文章导出为HTML并保存到文件系统; 2）向Internet Archive发出请求以抓取本文中的所有资源引用

Print打印

Requests to print the current document (window.print()). 请求打印当前文档(window.print())。

Edit编辑

Editor is one of the document modes a user can be in. The available features reflect the edit operation. Edits reside in the DOM until a Save or Save As is triggered. There are several editor features in following categories: content formatting and structuring (2, 3, 4, , , , , code, , , , , ), including interactive and embeddable objects (), inline semantic relations (), footnotes and citations (), and annotations (). 编辑器 是用户可以使用的文档模式之一，可能功能反映在编辑操作中。编辑驻留在DOM中直到 触发保存 或者 另存为 。有在以下几个类别的编辑器功能：内容格式化和结构(2, 3, 4, , , , , code, , , , , ), 包括交互式和可嵌入对象 (), 内联语义关系(), 脚注和引文(), 以及评注 ().

Source源

Users can edit the current state of the article. Updating, only updates the DOM, and leave the saving to Save or Save As. 用户可以编辑文章的当前状态。 更新，仅更新DOM，并将保存留给保存或 另存为。

Embed Data嵌入数据

This feature allows hidden RDF data to be stored with the document. Turtle, JSON-LD, and TriG can all be edited and stored independently. 此功能允许将隐藏的RDF数据与文档一起存储。Turtle，JSON-LD和TriG都可以独立编辑和存储。

To determine the base URL, when new documents are created or saved as, media resources from head link, [src], object[data] (querySelector) will have their URLs normalised to use current document's base URL as its absolute URL (this is the Use references as is option). If Copy to your storage is selected, relative URLs will not be updated as the copy operation reuses the same file paths when resource are copied to destination. The copy operation does an HTTP GET for each source, then HTTP PUT to target. 要确定基URL，当创建或保存新文档时，来自头链接的媒体资源，head link, [src], object[data] (querySelector) 将其URL标准化为使用当前文档的基URL作为其绝对URL（这是在使用引用作为选项）。如果选择“复制到你的存储”，则不会更新相对URL，因为复制操作会将资源复制到目标时重用相同的文件路径。该复制操作为每个源执行一次HTTP GET操作，然后HTTP PUT到目标。

The resource browser eg. available for New, Open, Save As operations can be used to navigate through a Webspace. It does this by using the Linked Data Platform's containment rules to retrieve and then display the container's index. If the user's personal storage location is known, it will be used as default location for the resource browser. Alternatively, if the article refers to an annotation service, it will be used as start location. 资源浏览器如，新建, 打开, 另存为操作可用于导航Webspace。它通过使用Linked Data Platform的包含规则来检索然后显示容器的索引来实现这一点。如果用户的个人存储位置已知，则它将用作资源浏览器的默认位置。或者，如果文章引用评注服务，则将它作为起始位置。

Users are given a choice to specify the rights and license for their annotations from a list of Creative Commons licenses, eg. CC BY 4.0. If applicable, the notification payload will use the CC0 1.0 Universal license. 用户可以从 创作共用 许可列表中指定标注的版权和许可证例如 CC BY 4.0，如果适用的话，通知负载将使用 CC0 1.0 Universal 许可证。

Views视图

The dokieli menu will list primary and alternate stylesheets that are detected in HTML. Native is always available and it will essentially disable all other stylesheets, thereby user-agent's default stylesheets are gets applied. When a view is selected, eg. Basic (which happens to be the one that is used on this article as primary), it becomes the primary stylesheet, and the rest of the stylesheets become alternate and disabled. dokieli菜单将列出在HTML检测到的主要和备用样式表。Native始终可用，它将基本上禁用所有其他样式表，从而应用用户代理的默认样式表。选择视图时，例如Basic （恰好是作为本文主要使用的那个）成为主要样式表，其余的样式表变为备用和禁用。