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
We should consider to supply the filename (maybe stripped of file extension) as seed metadata for Meta-ID creation if no other metadata can be acquired. In any case the order of operations to acquire seed metadata during automated ISCC creation should be part of the specification.
The text was updated successfully, but these errors were encountered:
You need to be very careful about this from a PII perspective, as filenames are frequently loaded with information that may be personalized and could expose unwanted information.
Yes that is an issue. But it is an issue for any kind of user generated metadata. We should add a warning in the specification. Something along the lines of:
"Implementations that support fully automated ISCC generation and expose both the ISCC and auto-generated metadata publicly must warn its users about potential privacy risks and require manual confirmation."
We should consider to supply the filename (maybe stripped of file extension) as seed metadata for Meta-ID creation if no other metadata can be acquired. In any case the order of operations to acquire seed metadata during automated ISCC creation should be part of the specification.
The text was updated successfully, but these errors were encountered: