xogeny / hyprofile Goto Github PK

As mentioned in #1, a specification might potentially be a sub-specification of one section of the API or of some isolated and reusable set of functionality. In order to promote reuse of such sub-specifications, I need to think about how one might import such sub-specifications.

At the moment, the profile lacks any kind of "entry point" URL. Normally, I would say that such a URL could simply be added as an additional property in the profile.json file. But I want to first spend some time thinking about how to handle composability (i.e., how to easily knit together multiple specifications to promote their reuse). It wouldn't make sense if each such specification had its own entry point (hence the inadequacy of just adding a new field and the need to think about this further).