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
I like urn:tripsu: but I want to see if there are best practices for crafting URN's. Maybe there is implicit meaning in the 'argument positions'. (like namespace:format in the case of urn:uuid or something). Don't want to accidentally introduce implicit meaning that we don't want.
Context:
Uniform Resource Name (URNs) are URIs that use the
urn
scheme without any prefix.Currently we hash the whole URI, and replace the fragment with the hash, retaining the original prefix. This poses 2 issues:
Proposed solution
Using URNs (format:
<urn:hash>
) as output would provide a solution to both issues as the pseudonymized data would not have a namespace.Objective: original domain is absent from pseudonymized URIs.
Requirements:
Hash
for rdf types -> urn:The text was updated successfully, but these errors were encountered: