For APP create (HTTP Post to the collection URL) operations, the default behavior of a plug-in is to register the URL of an existing feed hosted at an external location. A plug-in should override this default behavior by specifying a CollectionPlugin subclass.
The collection extension interface does not limit or restrict content of entry. When uploading binary artifacts (widgets, pages), they will be included as xsd:binary (BASE64 encoded) in an <archive>
element inside the <content>
element. The <archive>
element will have a "mimetype" attribute to pass the content-type of the binary attachment. For example, <catalog:archive mimetype="application/zip" filename="spacetemplate.zip"> [Base64 encoded string]</catalog:archive>
. When getting these entries from the collection, binary elements will be substituted with <downloadURL>
elements that can be fetched with extra HTTP request. Alternatively, the page, space, and iWidget plug-ins define a <packageURL>
element that provides a URL of the binary object that the plug-in can reference to read the object from its source. Finally, the page and iWidget plug-ins support a third approach, which allows the URL of the object to be registered to be passed in a <definitionURL>
element. Such registration does not involve an upload but corresponds to the Register iWidget
and Register Page
actions provided by the user interface.
The value of the <permission>
element in the entry being submitted can only be set to public
or to private
In general, MashupHub supports APP create operations for feed registration, uploading or registering an iWidget, uploading a generic widget, and uploading or registering a mashup page.
Parent topic: Catalog API: imc3