Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: use URNs as outputs #51

Open
2 tasks
cmdoret opened this issue Aug 13, 2024 · 3 comments
Open
2 tasks

feat: use URNs as outputs #51

cmdoret opened this issue Aug 13, 2024 · 3 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@cmdoret
Copy link
Member

cmdoret commented Aug 13, 2024

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:

  • we need to extract the prefix, which fails when urns are in the input
  • sensitive data may be present in the prefix. This should be removed

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:

  • Implement Hash for rdf types -> urn:
  • (optional?) additional method to hash with optional domain
@cmdoret cmdoret added the enhancement New feature or request label Aug 13, 2024
This was referenced Aug 13, 2024
@cmdoret
Copy link
Member Author

cmdoret commented Aug 13, 2024

Possible formats:
urn:<hash>
urn:tripsu:<hash>
urn:uuid:<uuid>

@rmfranken
Copy link
Member

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.

@cmdoret
Copy link
Member Author

cmdoret commented Aug 27, 2024

This would be a good opportunity to implement Hash on the individual RDF types

@cmdoret cmdoret added the good first issue Good for newcomers label Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants