Typed vs generic collections

Hello!

I've been taking a look at the two different Hydra example APIs (events and issues) and I had some questions about the way collections are handled. Apologies in advance if I'm using incorrect terminology here, I'm new to the linked data world.


In the events API the the collection of events is represented with an EventCollection class (type?) and in the Issues API example the Users and Issues are represented with a generic Hydra collection. The ApiDocumentation for EventCollection enumerates the operations that can be performed on that resource whereas the ApiDocumentation for the Issues API describes the operations that can be invoked on the users and issues properties in the context of the EntryPoint?.


The benefit of the former seems to be that if you have a response for an EventCollection type, your ApiDocumentation can tell you what operations you can invoke on that resource, whereas if you have a response for issues or users, without the added context of the EntryPoint, you can't see your available operations without navigating back.


Is one of these implementations preferred over the other? Is there a benefit to using a generic Hydra Collection in the case of the Issues API? Anything wrong with making all your collections typed for the sake of always having contextual operations present?


Thanks you!

Graham Conzett
Engineering Manager, Criteria Builder
866.452.5017
2 Miranova Pl., Columbus, Ohio 43215
www.covermymeds.com

This electronic transmission is confidential and intended solely for the addressee(s). If you are not an intended addressee, do not disclose, copy or take any other action in reliance on this transmission. If you have received this transmission in error, please delete it from your system and notify CoverMyMeds LLC at privacy@covermymeds.com. Thank you.