FsOboParser is a nice library which works fine but it lacks a bigger structure which is more divided into its core working parts.
That means, it would be nice to separate the library into the following parts (= individual projects):
FsObo, which inhabits the data model and all functions solely related to it
FsOboParser, which is merely the IO methods/functions
FsOboGraph, which consists of the OboOntology to FGraph functionality, currently implemented in ArcValidation's V2 branch
The name of this repo thus should be FsObo, and we also need to update the NuGet package accordingly.
(There was also the idea to use dotted namespaces: "FsObo.IO" for FsOboParser and "FsObo.Graph" for FsOboGraph but I would argue against that because in this case opening FsObo means polluting other .IO or .Graph namespaces (like System.IO) which is not nice.)
[ ] rename repo into FsObo
[ ] fill in base datamodel in eponymous project (rename FsOboParser project for that)
[ ] create new FsOboParser project with IO functionality
[ ] create new FsOboGraph project with OboOntology to Graphoscope.FGraph functionality
omaus
commented
10 months ago
FsOboParser is a nice library which works fine but it lacks a bigger structure which is more divided into its core working parts. That means, it would be nice to separate the library into the following parts (= individual projects):
The name of this repo thus should be FsObo, and we also need to update the NuGet package accordingly.
(There was also the idea to use dotted namespaces: "FsObo.IO" for FsOboParser and "FsObo.Graph" for FsOboGraph but I would argue against that because in this case opening FsObo means polluting other .IO or .Graph namespaces (like System.IO) which is not nice.)