[kukkeliskuu]

Great idea!

I was actually working on last weekend with something that has similarities. I am working on USM.tools, which allows specifying your services in structured way.

There is a need to specify some of the data in semi-structured way, and I am using markdown for that.

So there is this interesting relationship between unstructured, semi-structured and structured data, and markdown hits that middle ground.

Can I suggest you make some Jira etc. templates on your landing page clickable, so a visitor can grasp your idea more easily? For me it was not clear whether the specs are just plain markdown, or do you have some additional tagging there.

[zameermfm]

Great idea you got, what would be a classic use case? We have a data source and we can define the API structure to get them?

Sure! thanks! thats good idea, to have it clickable and true that needs needs to be easily understandable.

[kukkeliskuu]

Service management is business oriented, what is the service we are providing and how do we deliver it, and how do we agree with the customer what we deliver. And when the data is structured, other interesting oppurtinities become possible.

This particular use case is people working together to collect data in a workshop. 10 people don’t want to see somebody searching for the right place in a form, it interrupts the flow of the meeting. You need to capture the ideas raw, and then structure later. That is where question anout how unstructured data is captured in strucured format pops up.

It is a workflow I directly support in my tool, not a generic tool like yours.