diff --git a/fep/0837/fep-0837.jsonld b/fep/0837/fep-0837.jsonld
new file mode 100644
index 0000000..b636898
--- /dev/null
+++ b/fep/0837/fep-0837.jsonld
@@ -0,0 +1,23 @@
+{
+  "@context": {
+    "om2": "http://www.ontology-of-units-of-measure.org/resource/om-2/",
+    "vf": "https://w3id.org/valueflows/ont/vf#",
+    "Agreement": "vf:Agreement",
+    "Commitment": "vf:Commitment",
+    "Intent": "vf:Intent",
+    "Proposal": "vf:Proposal",
+    "action": "vf:action",
+    "availableQuantity": "vf:availableQuantity",
+    "hasUnit": "om2:hasUnit",
+    "hasNumericalValue": "om2:hasNumericalValue",
+    "purpose": "vf:purpose",
+    "publishes": "vf:publishes",
+    "reciprocal": "vf:reciprocal",
+    "resourceConformsTo": "vf:resourceConformsTo",
+    "resourceQuantity": "vf:resourceQuantity",
+    "satisfies": "vf:satisfies",
+    "stipulates": "vf:stipulates",
+    "stipulatesReciprocal": "vf:stipulatesReciprocal",
+    "unitBased": "vf:unitBased"
+  }
+}
diff --git a/fep/0837/fep-0837.md b/fep/0837/fep-0837.md
index 6481bd6..2825c12 100644
--- a/fep/0837/fep-0837.md
+++ b/fep/0837/fep-0837.md
@@ -1,10 +1,11 @@
 ---
 slug: "0837"
 authors: silverpill <@silverpill@mitra.social>
+type: implementation
 status: DRAFT
 dateReceived: 2023-08-17
 trackingIssue: https://codeberg.org/fediverse/fep/issues/147
-discussionsTo: https://codeberg.org/fediverse/fep/issues/147
+discussionsTo: https://socialhub.activitypub.rocks/t/fep-0837-federated-marketplace/3501
 ---
 # FEP-0837: Federated Marketplace
 
@@ -60,7 +61,7 @@ The representation of a proposal is a JSON document with the following propertie
 
 The representation of an intent is a JSON document with the following properties:
 
-- `id` (REQUIRED): the unique global identifier of the intent. Implementations SHOULD use URL fragments to identify intents associated with a given proposal. The RECOMMENDED fragment identifiers for primary and reciprocal intents are `primary` and `reciprocal`.
+- `id` (REQUIRED): the unique global identifier of the intent. Implementations SHOULD use URI fragments to identify intents associated with a given proposal. The RECOMMENDED fragment identifiers for primary and reciprocal intents are `primary` and `reciprocal`.
 - `type` (REQUIRED): the type of the object MUST be `Intent`.
 - `action` (REQUIRED): the type of economic transaction. The value of this property SHOULD be either `deliverService` or `transfer`.
 - `resourceConformsTo` (RECOMMENDED): the type of an economic resource. Could be any URI.
@@ -221,7 +222,7 @@ The representation of an agreement is a JSON document with the following propert
 
 **Commitments** are promised economic transactions. The representation of a commitment is a JSON document with the following properties:
 
-  - `id` (OPTIONAL): the unique global identifier of the commitment. This property is REQUIRED for commitments in finalized agreements. Implementations SHOULD use URL fragments to identify commitments associated with a given agreement. The RECOMMENDED fragment identifiers for commitments satisfying primary and reciprocal intents of the proposal are `primary` and `reciprocal`.
+  - `id` (OPTIONAL): the unique global identifier of the commitment. This property is REQUIRED for commitments in finalized agreements. Implementations SHOULD use URI fragments to identify commitments associated with a given agreement. The RECOMMENDED fragment identifiers for commitments satisfying primary and reciprocal intents of the proposal are `primary` and `reciprocal`.
   - `type` (REQUIRED): the type of the object MUST be `Commitment`.
   - `satisfies` (REQUIRED): the reference to an intent.
   - `resourceQuantity` (REQUIRED): the amount and unit of the economic resource.
@@ -309,6 +310,7 @@ Example:
   "result": {
     "type": "Agreement",
     "id": "https://market.example/agreements/edc374aa-e580-4a58-9404-f3e8bf8556b2",
+    "attributedTo": "https://market.example/users/alice",
     "stiplulates": {
       "id": "https://market.example/agreements/edc374aa-e580-4a58-9404-f3e8bf8556b2#primary",
       "type": "Commitment",
@@ -386,7 +388,7 @@ Example:
 
 ## References
 
-- Christine Lemmer Webber, Jessica Tallon, [ActivityPub][ActivityPub], 2018
+- Christine Lemmer-Webber, Jessica Tallon, Erin Shepherd, Amy Guy, Evan Prodromou, [ActivityPub], 2018
 - Lynn Foster, elf Pavlik, Bob Haugen, [Valueflows][Valueflows], 2023
 - Lynn Foster, [FEP-d767: Extend ActivityPub with Valueflows][FEP-d767], 2023
 - S. Bradner, [Key words for use in RFCs to Indicate Requirement Levels][RFC-2119], 1997