What are the minimum core requirements for APP introspection?
-
The location of APP collections (where to list and where to post)
-
Rationale: obvious.
-
Discussion:
-
The type of content an APP collection may contain
-
Rationale: clients need to know the nature of a given collection
-
Discussion: how granular does this need to be?
-
The APP collections available for a given user
-
Rationale: clients should be able to discover all collections available for a given user in order to simplify bootstrap and configuration
-
Discussion:
-
The logical arrangement of related APP collections
-
Rationale: GUI clients need to be able to present the available collections to users in a way that makes sense.
-
Discussion: is this needed for functional, organizational or presentational purposes?
-
Ability to express extended metadata about a collection
-
Rationale: GUI clients will likely need access to more information than just where to list and post and what types of content to post.
-
Discussion:
-
Lightweight
-
Rationale:
-
Discussion: this includes lazy loading if need be, but not lazy loading of huge feed documents just to get a couple of links
-
Extensible
-
Rationale:
-
Discussion:
-
Lends itself to deterministic action
-
Rationale: an APP client should be able to read an introspection document and then, automagically, decide what goes where.
-
Discussion:
