specification icon indicating copy to clipboard operation
specification copied to clipboard

Prefixes for Solid specs

Open csarven opened this issue 4 years ago • 4 comments

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

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

csarven avatar Sep 10 '21 13:09 csarven

Allright, works for me.

kjetilk avatar Sep 10 '21 13:09 kjetilk

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

pmcb55 avatar Sep 10 '21 14:09 pmcb55

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.

kjetilk avatar Sep 14 '21 09:09 kjetilk

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?

csarven avatar Sep 14 '21 10:09 csarven