xiekeyang

@wking , are you working on signature spec? I've read the sign issues and related technology. It seems that `merkle-dag` way is what you prefer to. Do you need some...

@wking May I take on this? I think I may implement signature spec and present a draft pr later, referred to issues discussion. Thanks a lot!

@wking , @opencontainers/image-spec-maintainers Here I want to confirm 3 points with you, thanks lots. ##### 1. signature target Technically, we can sign any object. But as the purpose of signature...

@opencontainers/image-spec-maintainers /cc @wking @stevvooe @philips @vbatts @runcom I investigate the technology and present my understanding here. It is my draft document, with brief description in each section. If there is...

@vbatts We might need more validation on JSON objects, besides `schema/*.json`, such as how to handle dis-matched result, and should valid child fields media-type if exist. Current `schema/validator.go` take some...

I remember we had discussed about the framework on validation, here I list them roughly, to help us for next improvement on `image-spec` and `image-tools`. Welcome forkers to add and...

> This is definitely going to impact the validation API. With you're giving up on #452 and #403 being closed, I think we're just waiting on the maintainers to show...

I would like to clear some questions about the design idea https://github.com/opencontainers/image-spec/issues/686#issue-231449187 . As comment on https://github.com/opencontainers/image-spec/pull/712#issuecomment-316282467, I have some question about the design : ### Question 1 ```go if...

@q384566678 For this issue we should make consensus the `Errors` and `Warns` type with required methods firstly. In specific API verifications, we should determine which errors should be ignored, and...

@wking If manifest, manifest list and single layer are unpackable? I'm not sure, but could you present some use case for that?