If you publish something online and want to declare that it is, say, open access, what do you do? You could just slap a Creative Commons logo on it, but these offer no guarantees - there are many cases where people have applied the license to content they don't own. This project addresses that problem. "CommonsDB uses a combination of cryptographic signatures and structured metadata to ensure the integrity and authenticity of content declarations." This post reports on the second phase of the feasibility study (49 page PDF) (the first was reported on last July). This phase "implemented the trust model in production, deployed three public APIs with a Developer Portal, enabled Data Suppliers to make live declarations, and launched the CommonsDB Explorer to expose registry content." It would be interesting to work with the APIs to both declare and use content. Related: Distributed Identity Foundation (DIF) Creator Assertions working group's user experience guidance document.
Today: Total: [Direct link] [Share]
