Byron Ruth

I closed it because it is simple enough to do outside of this library, however if it's built-in that would be great as well. Reopened for discussion.

Validation definitely needs to be optional to support your example. The idea is to simply have a `validate` method on `ProvRecord`, `ProvBundle`, or `ProvDocument` which, when called on an instance,...

> could you defined exactly what you mean by a valid record? I realized I still didn't answer your question. The spec defines which attributes are required and optional. For...

Using the PROV-JSON [schema](http://www.w3.org/Submission/2013/SUBM-prov-json-20130424/schema), the structure can be validated, i.e. whether the attributes are satisfied with the correct types, however there needs to be a second step of ensuring the...

@ethernetdan For schema validation, using [json-schema](http://json-schema.org/). [gojsonschema](https://github.com/xeipuuv/gojsonschema) is a library for doing this in Go. You can use it to validate that a JSON-LD record is valid as well as...

Hi @kba and @acdha I am cross-posting here from the issue @sevein referenced (visible above). https://github.com/archivematica/Issues/issues/583. I also want support for the fetch.txt file, however I only need/want validation and...

> Once the files have been downloaded, the regular bag validation process will handle it. We've been hesitant to put download support into bagit-python because it generally tends to get...

Ok understood. The #119 PR doesn't seem to validate the contents of the fetch.txt with respect to the manifest, so that could be a separate PR to perform that task,...

Right and the follow-up comment from @kba asserts the need to validate the fetch.txt file regardless if they are downloaded. Again for my use case, we don't want to download...

The use case I had in mind was actually to support alternate event timelines, i.e. branches that (in my case) would get merged/committed back into some _main_ repo I declare....