Make parser a stand-alone package

[Mec-iS]

The parser should be usable on its own outside of hydrus.
We need to find the cleanest way of porting the history in this repository and then build an interface (CLI) to make the parser usable as a stand-alone or library installable via pip from hydrus.

[shravandoda]

But as @xadahiya stated openAPI Parser imports hydrus as a dependency

[chrizandr]

But as @xadahiya stated openAPI Parser imports hydrus as a dependency

As mentioned here #2 (comment)

The parser only uses the tools in hydraspec. These are not strictly for hydrus only, you can use these tools as a separate library in itself. The idea now is to be able to use hydrus.hydraspec as a separate library.

@Mec-iS I also think that we should consider a repo for parsers in general, rather than having one for every different kind of parser. I remember writing one for OWL vocabularies as well, which is there in hydrus.hydraspec.legacy. Maybe have a repo for parsers in general? We can add more parsers to this package as we develop them.

[de-sh]

you can use these tools as a separate library in itself.

@chrizandr so, is hydra.hydraspec maintained as a separate repo/package? but metadata comes from hydrus namespace... so this is not really a possibility is it?

[shravandoda]

So how are we going to proceed? Do we make another repo for hydraspec and use it in hydrus and other parsers?

[Mec-iS]

in theory everything should be modular. should adapt this principle to practices.

i would create a repo python-hydra-core for hydraspecs.

[Mec-iS]

I moved the related code in this repo df27d30

[Mec-iS]

completed eea6a3e