Skip to content

Commit 7fbd159

Browse files
committed
remove outdated info on CreativeWork assertion
1 parent 34b53c6 commit 7fbd159

File tree

1 file changed

+0
-10
lines changed

1 file changed

+0
-10
lines changed

docs/faqs.mdx

Lines changed: 0 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -60,16 +60,6 @@ The [manifest](manifest/understanding.md) that defines the Content Credentials
6060
can include various assertions about the image, including the ingredients, the
6161
date and time, the location, and the device that created the image.
6262

63-
### How can I prove time and place an image was created without revealing my identity?
64-
65-
Content Credentials can specify identity by using the [Schema.org CreativeWork assertion](manifest/writing/assertions-actions.md#creative-work-assertion), but it is _entirely optional_.
66-
67-
For example, using Photoshop you
68-
can add Content Credentials that indicate what edits were made without saying who
69-
did it. You would know Adobe signed the Content Credentials and that's it. Regardless
70-
of the "who", the cryptographically-signed manifest ensures you know the date and
71-
time. A camera could also include Exif metadata with location information.
72-
7363
### How do you prevent faking GPS location metadata?
7464

7565
The location data included in [Exif metadata](manifest/writing/assertions-actions.md#exif-assertion) is based on the implementor. People would trust the data based on the various "trust signals" they are given in the manifest, such as who signed it and when.

0 commit comments

Comments
 (0)