Assess immediate gaps/shortfalls this types repository? #2
Description
Description
As we at KF are getting started with implementing tooling around DocMaps, one project is expressing the DocMaps standard in a format that is compatible with the RDF ecosystem of tools. RDF tools support ergonomic stream-like abstractions around linked data, so that we could for example have an ETL tool that ingests either docmaps or just sub-components of docmaps (like Steps or an individual Output) for composition or storage later. It is a reach goal to also use that representation to generate Typescript types.
From our conversation with eLife it seemed that a robust Typescript library for managing docmaps would be useful/is a need. This package already has a good amount of hand-rolled typing work, however, and I would love to know what your current issues with it are and so how we can help.
Are there problems you are facing or imagining facing, that this library can't solve for you? Are you facing problems with its completeness or ergonomics?