I agree. We don't need to put everything on 30382. 

What we do need is to specify what the "service" is calculating so that the user can chose which provider of that calculation they trust and clients can know what the value means.

There will be some differences between providers, but the goal and the final result spec (type, range, tags, etc) should be just one. 

Hopefully this NIP enables that multiple provider specification to come together.  

 >  final result spec (type, range, tags, etc) should be just one

Did I understand correctly - you want to include type, range, tags etc for each service into this NIP? 

 In the early days, yes. As it grows we can break it off. 

Right now we just need to start the work of specifying stuff.