URL structure about valueflo.ws

[ahdinosaur]

👍 for deep path option. also might be worth mentioning that i envision our docs being markdown files in valueflows/valueflows, which are built into html files and pushed to this repo.

[fosterlynn]

Yes, I do have on my list to add to the md file for Agent. Will try to get to today.

Although I will say that I'm probably more comfortable in html than in markdown.

At a certain level of complexity, might be easier to just maintain it in html?

Re. the options, you guys decide, it's above my pay grade. :)

[bhaugen]

@fosterlynn - I think we should stick with markdown. Sorry about that...😉

[fosterlynn]

@bhaugen Ha, no problem, you are allowed to disagree! I'm sticking with md for now in any case..... 😉

[ahdinosaur]

@elf-pavlik: does this mean we should change https://w3id.org/valueflows/ to point to https://valueflo.ws/ns/?

[elf-pavlik]

@ahdinosaur once we start responding there with something else than "Cannont GET ..." we should update the redirect, until then it doesn't really matter since all the data uses permanent https://w3id.org/valueflows/ prefix.

[almereyda]

We have moved the ValueFlows organization from GitHub to https://lab.allmende.io/valueflows.

This issue has been closed here, and all further discussion on this issue can be done at

https://lab.allmende.io/valueflows/valueflo-ws/-/issues/7.

If you have not done so, you are very welcome to register at https://lab.allmende.io and join the ValueFlows organization there.