Inverse of `hostsPoint`?

[jbkoh]

@gtfierro @fennibay sorry that I just found this while implementing something, but I guess better late than never.

Why is the inverse of hostsPoint isHostedBy? If we added Point suffix to hosts with the consideration of adopting other object types later, isHostedBy will be in conflict. Either we have to

• Change hostsPoint to hosts, or
• Change isHostedBy to pointIsHostedBy (or something better)

Any thoughts?

[fennibay]

Thanks @jbkoh. I agree that it should not be asymmetrical. I guess this can still be changed as this wasn't released yet.

Both options are fine.

I like the first option a bit better; because in the future we could extend the range of hosts with Functions etc. Similar to how feeds can target a brick:Equipment or a rec:Architecture.

[gtfierro]

I personally don't mind the asymmetry, but I'm open to changing.

We agreed on hostsPoint because we liked how the property indicated the type of thing you would find on the other end (ie a 'Point'). Then we could extend to hostsPointgroup, hostsFunction, etc. Do we want to keep hosts as a generic/extensible property the way that feeds is?