Merge branch 'main' into issue-482

Author: evanp

.github/workflows/fep-explainer.yml

@@ -0,0 +1,23 @@
+name: Add comment to explain Needs FEP label
+on:
+  issues:
+    types:
+      - labeled
+
+jobs:
+  add-comment:
+    if: github.event.label.name == 'needs-fep'
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+    steps:
+      - name: Add comment
+        run: gh issue comment "$NUMBER" --body "$BODY"
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_REPO: ${{ github.repository }}
+          NUMBER: ${{ github.event.issue.number }}
+          BODY: >
+            This issue has been labelled as potentially needing a FEP, and contributors are welcome to [submit a FEP](https://codeberg.org/fediverse/fep/src/branch/main#submitting-a-fep) on the topic.
+
+            Note that issues may be closed without the FEP being created; that does not mean that the FEP is no longer needed.

ERRATA.md

@@ -25,7 +25,7 @@ This document includes errata for the [Activity Streams](https://www.w3.org/TR/a
     are only allowed on `Link` objects. One alternative is to use `Link` objects
     with the correct `height` and `width` as the `url` property for each `Image`
     object.
-    
+
     ```json
     {
       "@context": "https://www.w3.org/ns/activitystreams",
@@ -60,14 +60,14 @@ This document includes errata for the [Activity Streams](https://www.w3.org/TR/a
   - The range of the `units` property is given as an enumerated set of values.
     Due to a formatting error, some of these values are shown with an incorrect
     leading space character. The correct range is:
-    
+
     ```text
     "cm" | "feet" | "inches" | "km" | "m" | "miles" | xsd:anyURI
     ```
 
   - Example 58 includes a `summary` property on a `Mention` object, which is
     not allowed. A corrected example:
-    
+
     ```json
     {
       "@context": "https://www.w3.org/ns/activitystreams",
@@ -79,6 +79,33 @@ This document includes errata for the [Activity Streams](https://www.w3.org/TR/a
 
   - Unlike `latitude` and `longitude`, the domain of the `altitude` term is the `Object` type. The `altitude` term should be included in the list of properties of an `Object`. Because `altitude` is primarily documented as a property of a `Place`, publishers should not include `altitude` on objects that are not of type `Place`, and consumers should accept objects with this property that aren't of type `Place`.
 
+  - Example 60, for the `Tombstone` type, is missing the `@context` property. The correct example should be:
+
+    ```json
+    {
+      "@context": "https://www.w3.org/ns/activitystreams",
+      "type": "OrderedCollection",
+      "totalItems": 3,
+      "name": "Vacation photos 2016",
+      "orderedItems": [
+        {
+          "type": "Image",
+          "id": "http://image.example/1"
+        },
+        {
+          "type": "Tombstone",
+          "formerType": "Image",
+          "id": "http://image.example/2",
+          "deleted": "2016-03-17T00:00:00Z"
+        },
+        {
+          "type": "Image",
+          "id": "http://image.example/3"
+        }
+      ]
+    }
+    ```
+
   - The domain of the `attributedTo` property is both `Link` and `Object`. `attributedTo` should be included in the list of properties of a `Link`.
 
   - The Notes for the `to` property do not correctly identify the functionality (one or more) of the values of the property. The notes should read: "Identifies one or more entities that are part of the public primary audience of this Object."
@@ -89,3 +116,45 @@ This document includes errata for the [Activity Streams](https://www.w3.org/TR/a
 
   - The Notes for the `bcc` property do not correctly define the range of the property, limiting it to only the `Object` type. The notes should read: "Identifies one or more entities that are part of the private secondary audience of this Object."
 
+  - The description of the `audience` property should read "Identifies one or more entities that represent the total population of entities for which the object can be considered to be relevant."
+
+  - Example 157 is not valid JSON because the `content` property extends over multiple lines. The correct example is:
+
+    ```json
+    {
+      "@context": "https://www.w3.org/ns/activitystreams",
+      "name": "A thank-you note",
+      "type": "Note",
+      "content": "Thank you <a href='http://sally.example.org'>@sally</a> for all your hard work! <a href='http://example.org/tags/givingthanks'>#givingthanks</a>",
+      "to": {
+        "name": "Sally",
+        "type": "Person",
+        "id": "http://sally.example.org"
+      },
+      "tag": {
+        "id": "http://example.org/tags/givingthanks",
+        "name": "#givingthanks"
+      }
+    }
+    ```
+
+  - Example 102 is missing a `type` property on the `Link` value of the `url` property. For clarity, the example should read:
+
+    ```json
+    {
+      "@context": "https://www.w3.org/ns/activitystreams",
+      "type": "Video",
+      "name": "Cool New Movie",
+      "duration": "PT2H30M",
+      "preview": {
+        "type": "Video",
+        "name": "Trailer",
+        "duration": "PT1M",
+        "url": {
+          "type": "Link",
+          "href": "http://example.org/trailer.mkv",
+          "mediaType": "video/mkv"
+        }
+      }
+    }
+    ```

LICENSE.md

@@ -0,0 +1,19 @@
+This work is being provided by the copyright holders under the following license.
+
+# License
+
+By obtaining and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions.
+
+Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the work or portions thereof, including modifications:
+
+- The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
+- Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, the W3C Software and Document Short Notice should be included.
+- Notice of any changes or modifications, through a copyright statement on the new code or document such as "This software or document includes material copied from or derived from [title and URI of the W3C document]. Copyright (c) [YEAR] W3C® (MIT, ERCIM, Keio, Beihang)."
+
+# Disclaimers
+
+THIS WORK IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENT WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
+
+COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENT.
+
+The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the work without specific, written prior permission. Title to copyright in this work will at all times remain with copyright holders.

README.md

@@ -1,12 +1,103 @@
-# Activity Streams 2.0 Editor's Drafts
+# Activity Streams 2.0
 
-Contributions to this specification are governed by the W3C 
-IPR Policy. Pull requests will be accepted only if the 
-submitter is a current member of the W3C Social WG but 
-issues can be opened by anyone.
+Activity Streams 2.0 (AS2) is a social data format. Its types represent activities, content objects, and actors like people or groups on the social web.
 
-## Implementations
+It is an extensible format; the Activity Vocabulary provides a structure for social applications, but more focused or innovative objects can be represented in AS2 by extending the vocabulary.
 
-Recent implementation summary: https://www.w3.org/2017/02/social/implementations/as2/
+## Key Links
 
-Please report your implementations and test results as a pull request on a new file in [implementation-reports](https://github.com/w3c/activitystreams/tree/master/implementation-reports), using the format of [template.md](https://github.com/w3c/activitystreams/blob/master/implementation-reports/template.md).
+* The [Core specification](https://www.w3.org/TR/activitystreams-core/) describes the basic structure of AS2 and the core classes like `Object` and `Link`.
+* The [Vocabulary specification](https://www.w3.org/TR/activitystreams-vocabulary/) expands on the core specification with definitions of several dozen activity and object types, as well as many properties of those types.
+* The [SocialCG](https://www.w3.org/Social/WG) is the W3C Social Web Working Group, which is the home of AS2.
+* [ActivityPub](https://www.w3.org/TR/activitypub/) is a protocol that uses AS2 for communication between social systems.
+* The [Activity Streams Primer](https://www.w3.org/wiki/Activity_Streams/Primer) includes some expanded examples and explanations of AS2. If it's unclear how to use a type or property, the primer is a good place to start.
+* The [Extensions registry](https://www.w3.org/wiki/Activity_Streams/Extensions) lists known extensions to AS2.
+* Popular extensions can be integrated into the AS2 vocabulary document, making them practically part of the spec. The [Extensions Policy](https://swicg.github.io/extensions-policy/) describes how to propose extensions for inclusion in AS2.
+
+## Editors
+
+The currently active editors of the AS2 specification(s) are:
+
+- [Evan Prodromou](https://github.com/evanp)
+
+## Supported deliverables
+
+These files are maintained by the editor(s) under the supervision of the SocialCG:
+
+* The Core specification.
+* The Vocabulary specification.
+* The JSON-LD context document.
+* The OWL ontology document.
+
+The documentation is primary; the JSON-LD context and OWL ontology follow from the documentation.
+
+Other documents included here are informational and provided on a best-effort basis, or to support the processes of the W3C.
+
+## Contributions
+
+Because AS2 is a W3C Recommendation, its published documents are stable and changes are highly controlled. If you'd like to contribute, the best way is to open a [GitHub issue](https://github.com/w3c/activitystreams/issues) or join the [SocialCG](https://www.w3.org/Social/WG) and participate in discussions there.
+
+Pull requests are generally *not* helpful, unless you're an editor or have been asked to submit a pull request by an editor. The editors are responsible for the content of the documents, and they will make changes based on the issues and discussions.
+
+AS2 provides the vocabulary for ActivityPub, but many of the protocol details are not part of AS2. Issues with the protocol and ActivityPub API should be created in the [ActivityPub repository](https://github.com/w3c/activitypub). If you're not sure, it's okay to open an issue in the AS2 repository and the editors will navigate it to the right place.
+
+## Processes
+
+### Questions and clarifications
+
+If you have a question about the specification(s), including text or terms that are unclear or ambiguous, please open a [GitHub issue](https://github.com/w3c/activitystreams/issues).
+
+Clarifying questions may influence future versions of the document, but they aren't usually treated as errors that need to be updated as errata. A typical resolution for a clarifying question is to add a page to the [Activity Streams Primer](https://www.w3.org/wiki/Activity_Streams/Primer).
+
+### Editorial changes
+
+If you find a textual error in the specification(s), please open a [GitHub issue](https://github.com/w3c/activitystreams/issues). Examples of textual errors:
+
+- Spelling mistakes
+- Grammar mistakes
+- Broken links
+- Incorrect references to other parts of the document
+- Semantic mistakes
+- Misleading or confusing language
+- Syntax errors in the JSON-LD of examples in the documents
+
+The process for making editorial changes is as follows:
+
+1. A GitHub issue is opened.
+2. Participants discuss the issue in the comments.
+3. The editor(s) open a pull request to add the correction to the ERRATA document.
+4. At a future meeting of the SocialCG, the editor(s) propose to accept the pull request. The SocialCG discusses the proposal and votes to accept or reject it.
+5. If it's accepted, the editor(s) merge the pull request and close the issue.
+6. The editor(s) update the editor's draft of the document to include the correction.
+7. Periodically, updated non-normative editorial changes are published as a new version of the document at the canonical URL.
+
+### Backwards-compatible changes
+
+Social networking changes every year, and AS2 is designed to be keep up with that pace of change. Backwards-compatible changes are those that don't break existing implementations of AS2.
+
+The most important type of backwards-compatible normative change is adding types and properties to the vocabulary.
+
+The primary way to create a backwards-compatible change is to create a new extension to Activity Streams 2.0. You can create a GitHub issue to discuss the extension idea, which can help with building consensus around the change.
+
+Extensions are documented on the [Extensions registry](https://www.w3.org/wiki/Activity_Streams/Extensions). Before starting a new extension, it's a good idea to check the registry to see if someone else has already created a similar extension.
+
+The [Fediverse Enhancement Proposals](https://codeberg.org/fediverse/fep) process is a lightweight collaboration process for creating and documenting Activity Streams 2.0 extensions (and other changes to the Fediverse). It's a good place to start if you're considering a backwards-compatible change.
+
+There are many ideas for backwards-compatible changes to ActivityPub that have not yet been written up as a FEP or other document. These are marked [Needs FEP](https://github.com/w3c/activitystreams/issues?q=is%3Aissue+label%3A%22needs-fep%22) in the ActivityPub GitHub issue repository, and contributors are welcome to [submit a FEP](https://codeberg.org/fediverse/fep/src/branch/main#submitting-a-fep) on the topic. Note that issues may be closed without the FEP being created; that does not mean that the FEP is no longer needed.
+
+Extensions that become popular can be integrated into the AS2 vocabulary document, making them practically part of the spec. The [Extensions Policy](https://swicg.github.io/extensions-policy/) describes how to propose extensions for inclusion in AS2.
+
+Future versions of the AS2 specification(s) may include popular extensions as part of the core specs; see below.
+
+### Non-backwards-compatible changes
+
+Non-backwards-compatible changes to the specification require chartering a new working group at the W3C. They also require making changes in dozens of ActivityPub implementations and tens of thousands of running servers. This is a lot of work and is not done lightly.
+
+Non-backwards-compatible changes include:
+
+- Making optional behaviour mandatory
+- Loosening requirements for existing types or properties
+- Deprecating types or properties
+- Removing types or properties from the vocabulary
+
+If you think a non-backwards-compatible change is necessary, please open a [GitHub issue](https://github.com/w3c/activitystreams/issues) to discuss it. It will be marked as a "next version" issue, so when a new working group is chartered, the issue can be considered for the new version of the specification(s).