Prefixes for Solid specs

solid / specification

Solid Technical Reports

https://solidproject.org/TR/

MIT License

486 stars 46 forks source link

Prefixes for Solid specs #308

Open csarven opened 3 years ago

csarven commented 3 years ago

Just placeholder/consideration space for prefixes that we can use for Solid specs:

Solid Protocol: sopr
Solid WAC: sowac
Solid OIDC: sooidc

kjetilk commented 3 years ago

Allright, works for me.

pmcb55 commented 3 years ago

Just my 2c, but I much prefer readable/more meaningful prefixes, and don't fear longer ones (look at FIBO for instance!). So I'd suggest:

Solid Protocol: solid_protocol
Solid WAC: solid_wac
Solid OIDC: solid_oidc

kjetilk commented 3 years ago

Just my 2c, but I much prefer readable/more meaningful prefixes, and don't fear longer ones (look at FIBO for instance!). So I'd suggest:

Uuuuh, you spooked me, @pmcb55 ;-) I'm going to type these a lot in my tests, I'd like them short. I guess it depends a lot on circumstance, if you're coding or if you're trying to explain something. In this case, it isn't even a vocab.

csarven commented 3 years ago

Naming things is hard. I prefer them short while aiming to be consistent / "automatically" constructable given input. So, the initial proposal is a bit inconsistent in that regard with eg. "sopr". It should be "soprotocol" to match the rest. Or the pattern should be like "so" + first n characters. "so" + last path segment makes sense in that we are using "shortnames" after /TR/. That means we could use soprotocol, sowac, soidc.

Pat, where would you be using these?