solid-spec icon indicating copy to clipboard operation
solid-spec copied to clipboard

SOLID as a protocol to indentify researchers

Open jibe-b opened this issue 8 years ago • 7 comments

In France there are discussions around the different protocols to be used to identify researchers on the web. See https://hyp.is/NvlrzjrgEeeYfC-NJAwf6w/association.dissem.in/files/pv-ag-2016.pdf for example

It may valuable to promote SOLID to dissem.in HAL.archives-ouvertes.fr etc

jibe-b avatar May 17 '17 09:05 jibe-b

  • Blockcerts:
    • JSON-LD documents signed with [parametrized] ld-signatures stored in the Bitcoin blockchain (< 1MB).
    • Homepage: http://www.blockcerts.org/
    • Src: https://github.com/blockchain-certificates
    • Src: https://github.com/blockchain-certificates/cert-schema
    • Notes re: schema.org/Certificate, CTI, WebID and other existing linked data credential specs:
      • https://github.com/blockchain-certificates/cert-schema/issues/25#issuecomment-288611927 https://github.com/blockchain-certificates/cert-schema/issues/25#issuecomment-289006903

westurner avatar May 23 '17 17:05 westurner

  • Keybase
    • Homepage: https://keybase.io/
    • Src: https://github.com/keybase
    • https://keybase.io/docs/server_security/merkle_root_in_bitcoin_blockchain
      • https://github.com/keybase/blockchain-tools

westurner avatar May 23 '17 17:05 westurner

May I ask how you consider mixing Solid and a blockchain?

jibe-b avatar May 23 '17 17:05 jibe-b

Credentials used to sign LDPRs in a SOLID LDPC would be stored in a Blockchain (and so the trust root would then be resilient, distributed, and validatable).

On Tuesday, May 23, 2017, jibe-b [email protected] wrote:

May I ask how you consider mixing Solid and a blockchain?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/solid/solid-spec/issues/102#issuecomment-303471965, or mute the thread https://github.com/notifications/unsubscribe-auth/AADGy3xeeypChi7nFJYGlwmPTG91-Pl8ks5r8xVzgaJpZM4NdlHD .

westurner avatar May 23 '17 18:05 westurner

Clear, thank you.

jibe-b avatar May 23 '17 19:05 jibe-b

IDK who's solved for the key lifecycle? As far as processes:

  • Create a new Credential (URI, keypair, [metadata])
  • Validate a Credential ld-signature with a trust chain (leading to a trust root)
  • Store a Credential for easy retrieval
    • DHT, blockchain
    • Datastore
      • LDP (SOLID)
  • Retire expired/lost Credentials
    • How do key rotation and expiration work with: (CRL & OCSP, blockchain) (or indeed with existing solutions for data-in-motion and data-at-rest)?
      • Because the blockchain solves the double-spending problem, an is8601 expireDate datetime (in a signed record) should be sufficient for expiry (if that's even relevant to academic credentials which link an individual to an organization over one or more segments of time)
      • IIUC, IDK, Revocation is harder with just a blockchain: who retains the ./#revokeCredential privilege for a Credential granted from which entity?

From http://www.blockcerts.org/guide/ :

These open-source repos form a working standard for blockchain certificates that may be utilized by other research projects and commercial developers. It contains components for creating, issuing, viewing, and verifying certificates using the Bitcoin blockchain. These components form all the parts needed for a complete ecosystem.

Please note that this standard is not attempting to solve identity. In other words, this solution does not certify the mapping of public keys to individuals or organizations. However, this ecosystem does form the basis for making strong proof of claims.

westurner avatar May 24 '17 12:05 westurner

@jibe-b Perhaps more immediately practical: The linked PDF mentions ORCID (for individuals, I assume). (Unfortunately, it's too difficult to translate a PDF):

https://en.wikipedia.org/wiki/ORCID

  • https://orcid.org/
    • http://orcid.org/0001-0001-0001-0001
    • https://orcid.org/statistics
  • https://schema.org/Person
    • https://schema.org/identifier ?
{"@context": "http://schema.org/",
 "@graph": [
     {"@type": "Person",
      "name": "firstname lastname"
      "identifier": {"@type": "PropertyValue",
          "propertyId": "ORCID",
          "value": "http://orcid.org/0001-0001-0001-0001"}}
 ]
}

And then there's DOI (Digital Object Identifier):

  • https://en.wikipedia.org/wiki/Digital_object_identifier
  • "How do I get a DOI for a dataset?" https://academia.stackexchange.com/questions/52032/how-do-i-get-a-doi-for-a-dataset
    • {Figshare (free), Zenodo (free), Dryad}
  • And then, schema.org/CreativeWork :
    • https://schema.org/CreativeWork
      • https://schema.org/Article
        • https://schema.org/ScholarlyArticle

With the eventual goal of producing a citation graph from resources described with linked data and linked by reified edges with provenance information: https://wrdrd.github.io/docs/consulting/linkedreproducibility#studygraph-document-nodes-and-link-edges

A practical concern:

  • How many credentials does a researcher accumulate over a given career?

westurner avatar May 24 '17 13:05 westurner