provenance_domain obsolete or obsolete_after

biocompute-objects / BCO_Documentation

Repository for documentation to support the IEEE 2791-2020 standard. Please see our home page for communications/publications:

http://biocomputeobject.org/

BSD 3-Clause "New" or "Revised" License

16 stars 12 forks source link

provenance_domain obsolete or obsolete_after #38

Closed corburn closed 6 years ago

corburn commented 6 years ago

The specification uses obsolete, but the schema uses obsolete_after:

./base_type_BioCompute.json:89: "obsolete_after" : { ./provenance-domain.md:17: "obsolete" : "2118-09-26T14:43:43-0400", ./provenance-domain.md:105:### 2.1.6 Obsolescence "obsolete" ./provenance-domain.md:110:"obsolete" : "2118-09-26T14:43:43-0400" ./HCV1a.json:33: "obsolete" : "2118-09-26T14:43:43-0400", ./user_guide.md:242: "obsolete_after" : { ./user_guide.md:461: "obsolete" : "2118-09-26T14:43:43-0400",

HadleyKing commented 6 years ago

obsolete_after is more informative

corburn commented 6 years ago

missed 2 references in e4688f1:

[x] ./base_type_BioCompute.json:89: "obsolete_after" : {
[x] ./provenance-domain.md:17: "obsolete" : "2118-09-26T14:43:43-0400",
[x] ./provenance-domain.md:105:### 2.1.6 Obsolescence "obsolete"
[x] ./provenance-domain.md:110:"obsolete" : "2118-09-26T14:43:43-0400"
[x] ./HCV1a.json:33: "obsolete" : "2118-09-26T14:43:43-0400",
[x] ./user_guide.md:242: "obsolete_after" : {
[x] ./user_guide.md:461: "obsolete" : "2118-09-26T14:43:43-0400",