- From: Alex Jackl <alex@bardicsystems.com>
- Date: Tue, 22 May 2018 13:28:28 -0400
- To: Phil Barker <phil.barker@pjjk.co.uk>
- Cc: public-eocred-schema@w3.org
- Message-ID: <CAGHXJihw6kWJnxV1s2FvJ9uexKw3xD6tmVKF7vUBVtTFu0RSEA@mail.gmail.com>
I agree. I didn't understand the argument about it blocking future use because in the way it was being defined obligations and verifications were two separate "things". Alexander Jackl CEO & President, Bardic Systems, Inc. alex@bardicsystems.com M: 508.395.2836 O: 401.384.0566 F: 617.812.6020 http://bardicsystems.com On Tue, May 22, 2018 at 1:25 PM, Phil Barker <phil.barker@pjjk.co.uk> wrote: > Thank you Nate. I understand your reluctance to accept unverified > statements of recognition for your use cases and appreciate your agreement > not to block their use for other cases (where I think verification can be > by other means). > > I don't think here is the right place to go into details of how our > proposal would work with any future development of verifiable endorsements, > but I think there are a couple of options: either using a pattern similar > to that shown <http://blog.schema.org/2014/06/introducing-role.html> by > Role <http://schema.org/Role> where an intermediate schema.org type can > provide additional information about a relationship (the AlignmentObject > does something like this too), or by creating new verifiedRecognition > property. I am confident therefore that having recognizedBy as a property > won't prejudice any future efforts to verify such a claim. > > Regards, Phil. > > On 22/05/18 15:49, Nate Otto wrote: > > For me, the verifiable endorsements are the only type of recognition that > I would trust. I won't block the inclusion of recognizedBy, but structuring > the relationship as RecognizedEntity.recognizedBy -> RecognizingEntity > doesn't allow for the relationship to flow through a specific verifiable > record describing that recognition. I think the > RecognizedEntity.endorsements -> Endorsement -> Endorsement.issuer -> > RecognizingEntity allows us to describe the scope or purpose the credential > or other entity is recognized for. > > Nate Otto > Director, Open Badges, Concentric Sky > concentricsky.com > he/him/his > > > -- > > Phil Barker <http://people.pjjk.net/phil>. http://people.pjjk.net/phil > PJJK Limited <https://www.pjjk.co.uk>: technology to enhance learning; > information systems for education. > CETIS LLP <https://www.cetis.org.uk>: a cooperative consultancy for > innovation in education technology. > > PJJK Limited is registered in Scotland as a private limited company, > number SC569282. > CETIS is a co-operative limited liability partnership, registered in > England number OC399090 >
Received on Tuesday, 22 May 2018 17:28:54 UTC