This is a good question and I would be interested in the answer. We're working with a collaborative industry group on JSON Schema specifications, and it would make sense to reference or include this metadata library rather than recreate it.
Our chosen licence is the Apache 2.0 licence because we recognise that commercial implementers who develop software using the specifications might also need to publish their API specifications, which might necessitate "publishing the library" as a derivative work. Under Apache 2.0 they could use their own licence for their pieces and Apache for our specifications, while under LGPLv3 everything would need to be under LGPLv3.
This is a good question and I would be interested in the answer. We're working with a collaborative industry group on JSON Schema specifications, and it would make sense to reference or include this metadata library rather than recreate it.
Our chosen licence is the Apache 2.0 licence because we recognise that commercial implementers who develop software using the specifications might also need to publish their API specifications, which might necessitate "publishing the library" as a derivative work. Under Apache 2.0 they could use their own licence for their pieces and Apache for our specifications, while under LGPLv3 everything would need to be under LGPLv3.