|home||specifications||WIJIS URIs||gateway||CDCL||GJXDM example||warrants/po exchange||wijis articles|
A type is the definition of common attributes or qualities shared by instances of information, and the type is used to distinguish those instances from other information. The type definition can be coupled to information (numeric, alphabetic, symbolic, composites, more complex things, anything at all). This coupling occurs by closely associating pertinent information with a mark-up tag, which identifies the type definition URI/URL.
Confirmation occurs with a status code (SUCCESS/OK) and with returned information (an entity-body) comprised of:
Refutation occurs with a status code (NOT FOUND).
It is permissible for a typedef registry to respond with a redirection status code (analogous to http status 3xx), which means that the client must take additional action in order for the request to be processed.
And of course, a typedef registry can respond in other ways or with other status codes should appropriate conditions warrant doing so.
A typedef registry may elect to accept candidate registry entries from anonymous sources or may elect to accept such candidate entries from only certain, identified, and/or trusted populations.
In all cases, candidate entries are administratively reviewed for well-formedness, for non-redundancy, for fitness to the given registry, and for valid semantic references when present. Only after diligent review should an administrator approve or deny registration of the candidate entry. Only approved candidates entered into the registry may have confirmation responses provided to any requests of that entry's URI/URL.
At minimum, this strongly secured connection would convey a message digest or hash of the requests and responses and would authenticate the registry to the client. Privacy, authentication of the client to the registry, and non-repudiation may be optionally employed.
At minimum, the registry shall provide a web application facade for the purpose of browsing the registry's contents. This way, rulesheet authors, document primary custodians, and providers of user context and client context can understand the landscape of registry entries that is available for use.