[Feature Request] Export Option SpecIf from HTML with embedded SpecIF

[milWien]

It would be nice if we could export a specif file back from a HTML with embedded SpecIF.

Use Case:

1. Writing the Spec.
2. Sending the Spec with editor rights as one HTML file to Customer (no program/webservice needed to open and edit)
3. Customer Exports again as HTML or directly as SpecIF
4. Customer sends changes back
5. We can export as SpecIF again and see the diff in a diff viewer and check the changes made.

[odungern]

Hi, milWien (sorry, don't have a name),
... that can be implemented without too much of an effort. I'd be interested, what you are up to! Short tele-conference?
Oskar

[milWien]

Hi Oskar,
i Closed the issue as i saw there is no further development on this, based on the Readme. And sadly i didn't find the v1.2 which was already online on your webside.
https://specif.de/v1.2/apps/edit.html#view=import

I am working for a small german business producing hardware and software components on project basis.

We are still in the excel requirments hell and i found by acciedent that Doxygen now has the ability to trace requirements between implementation and tests. That triggered me to search a bit for options handling requirements in a machine readable format. As the idea was that we have a single source of truth reqirement file and then we generate the software requirement as doxygen texts from it to have them within our doxygen c-code documentaion with the new tracability features.

The thing why we never changed from excel is because we need something our customers can easily modify and check without installing a other program. So even ReqIF itself as a sharing format failed. As they don't have the options to edit it.

As i saw the implementation of the single HTML which can edit the specif. I thought that might be it as it ships editor + data together within one file, which we could send via mail to our customers.
But then i found that if i am once within this format i never get out of it anymore. Thats why the export to at least the .specif file would be nice. So i can export the specif file from the finally approved html file, check both into my git repo, and auto generate the doxygen part for my software repo (we obviously have software and hardware requirements and therefore i only want to have the software part synced in my software repo)

But this are currently only ideas, and with the read of your Readme i also saw this repo wants to be a reference implemtation not production ready. Therefore i also though about if i would use reqif but then i would need to build all the web edit and one file thing myself.

Greetings
Sven

[odungern]

Hi, Sven,
.. thanks for your interest and explanations. I were happy if more people understood how simple an all-digital thread can be realized and an easy-to-use UI for customers at the same time.

Status of SpecIF: Indeed, the open repo at GfSE has been abandonded (can give reasons in a teleconference). A new private repo has been opened by my company. There is an openly accessible deployment of the SpecIF-Editor and there is further development as needed (SpecIF-Editor-alpha). More importantly, the experiences made with SpecIF find their way in the international standardization initiative CASCaRA at OMG ... which will eventually replace SpecIF. No fears: All data can be migrated from SpecIF to CASCaRA.

You are asking for a way to extract data from an HTML with embedded SpecIF. Can be done with a day of effort (or less). Even more easy would be to save SpecIF from the HTML - in that case you would have to ask your customer to return the .specif.zip file after entering the comments.

Open source works by giving and taking ... would your company be ready to either contribute with time or budget? Not much needed for this change ... you can get a deployment package, of course, to be independent of our installation.

Oskar