From 78933e24c4d9469e41a0fbbb97f4e0784a1b9c04 Mon Sep 17 00:00:00 2001 From: nsheff Date: Wed, 12 Jun 2024 08:29:59 -0400 Subject: [PATCH] fix markdown rendering --- docs/seqcol_rationale.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/seqcol_rationale.md b/docs/seqcol_rationale.md index 7e67ddf..ca72d04 100644 --- a/docs/seqcol_rationale.md +++ b/docs/seqcol_rationale.md @@ -7,7 +7,7 @@ The Refget Sequence Collections standard specification is written mostly to answ More specifically, this document attempts to answer these questions: - Why should the specification include a specific recommended schema, with a defined set of terms, including which are *required* (must exist) and which are *inherent* (affect the outcome of the digest)? -- Why is there not a digest for , so I can just compare two strings to see if the sequence collections are the same? Why do you need these more complex digests that make my comparison harder? +- Why is there not a digest for ``, so I can just compare two strings to see if the sequence collections are the same? Why do you need these more complex digests that make my comparison harder? - What is the purpose of the comparison function, which seems more complicated than a simple string match? - Why do you organize the sequence collection as a set of arrays, instead of an array of annotated sequence objects? - Why do you do repeated layers of digests, instead of just building one string for the collection and digesting it, which seems simpler?