You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/faqs.mdx
-10Lines changed: 0 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,16 +60,6 @@ The [manifest](manifest/understanding.md) that defines the Content Credentials
60
60
can include various assertions about the image, including the ingredients, the
61
61
date and time, the location, and the device that created the image.
62
62
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
-
73
63
### How do you prevent faking GPS location metadata?
74
64
75
65
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