URL for the vocabulary - Githubissues

fosterlynn commented 8 years ago

We'll need to host the vocab somewhere. Like the context and the documentation.

Isn't there some service for hosting random vocabularies? Or should we pony up for a domain name and use someone's server? Or are we connected enough to w3c?

The URL will need to be kind of permanent.

ahdinosaur commented 8 years ago

i'll host a server, we cool with openvocab.is?

fosterlynn commented 8 years ago

Let's think about the name - see issue #22

But also - awesome @ahdinosaur !

ahdinosaur commented 8 years ago

as mentioned in https://github.com/openvocab/definition/issues/2, it's probably easiest if we host it on GitHub pages, so that way it is automatically linked in with our GitHub org and repos.

elf-pavlik commented 8 years ago

I recommend https://w3id.org/ which in turn can redirect to openvocab.is

@ahdinosaur If we prefer to use independent domain for namespace, I would propose requirement of registering it for min 5 years and at least 3 people having admin access to manage it!

almereyda commented 8 years ago

Any reason why purl.org would be out of the game?

It has some use http://lov.okfn.org/dataset/lov/vocabs/essglobal

But can be any domain, and especially in terms of autonomy, a GitHub distangled hosting can also have its upsides.

fosterlynn commented 8 years ago

@almereyda Yes, I've seen it while poking around for vocabs. Do you think it will be around for a while? Do you know who runs it, pays for it, etc.? (So I don't have to do my own research... :smile: )

elf-pavlik commented 8 years ago

this article also tries to answer question "Why not purl.org" http://manu.sporny.org/2013/perma-id/

fosterlynn commented 8 years ago

So, here is a proposal, based on what has been discussed and linked.

First, about the URL that everybody would see and use into the future:

I'm hesitant to use github because it is not open source, seems like the wrong way to go long term.
I don't have a need for our own domain name if we can count on something else that is basically supporting the commons to remain alive. And really, it might be more risky for our little vocab to have its own place, since we are few and just starting.
I'm good with w3id.org based on elf's recommendation and link, vs purl.org.

So using w3id.org would also require that we put it somewhere, as it is basically a redirection service. Github pages would seem fine for that for now, if that is the easiest.

What do you all think?

ahdinosaur commented 8 years ago

@fosterlynn :+1: for the proposal.

ahdinosaur commented 8 years ago

forked w3id.org and added valueflows. @elf-pavlik can i haz a review before i squash and pull request? i'm also open to waiting until we have more to show in case this invites attention.

elf-pavlik commented 8 years ago

@ahdinosaur LGTM please squash & make PR :+1:

ahdinosaur commented 8 years ago

success! our URL is now http://w3id.org/valueflows/. :)

elf-pavlik commented 8 years ago

success! our URL is now http://w3id.org/valueflows/. :)

Let's all please use HTTPS https://w3id.org/valueflows/

http://www.w3.org/2001/tag/doc/web-https

almereyda commented 8 years ago

Can I assist in setting up TLS for https://valueflo.ws, which doesn't work yet? It seems we should make it available right from the start, so no http links get spawned over the web.

On 5 October 2015 at 12:06, elf Pavlik notifications@github.com wrote:

success! our URL is now http://w3id.org/valueflows/. :)

Let's all please use HTTPS https://w3id.org/valueflows/

http://www.w3.org/2001/tag/doc/web-https

— Reply to this email directly or view it on GitHub https://github.com/valueflows/agent/issues/23#issuecomment-145486044.

fosterlynn commented 8 years ago

@almereyda sounds like a good idea. Does the certificate cost much?

elf-pavlik commented 8 years ago

let's make a new issue for that in https://github.com/valueflows/valueflo.ws ?

ahdinosaur commented 8 years ago

@fosterlynn made an issue here.

valueflows / agent

URL for the vocabulary #23