| ID | 1.4.7 |
| Title | Transparency and ease of use of content and service creation and deployment tools to all parties on the platform |
| Expert | Michaël Van Bossuyt (VUB) Pieter Ballon (VUB) |
| Priority | mandatory |
| Description | Content providers (professional, semi-professional or amateur) desire easy-to-use content and service publishing tools. Transparency of the platform through for example standardized or easy-to-grasp input interfaces is one way to realize such ease-of-use, as content and service providers no longer have to deal with the platform as such. |
| Rationale | An a priori requirement of the platform is to simplify the use of services, platforms and devices to a wide range of parties. The platform should be easily accessible to third parties (such as telecom operators not involved in the creation and operation of the platform, content providers, application service providers, aggregators of content and services, end users and so on), be they professional, semi-professional or amateur. Transparency could allow them to consider the platform a black box that takes care of the necessary steps to provide content or services to consumers, with indifference to the underlying architecture. This is especially true for edge content providers, whom content creation is not a core competence (e.g. BMW, Unilever, Heineken, Jeep, and so on, who all provide content in which their products are involved, without the production of this content being a core competence nor a core business). For these providers, not the content itself is important, but rather the effects that are derived from it. A lack of skills and/or resources (for example for individuals or semi-professional providers) could be a reason for non-participation of these parties. An easy-to-use platform could overcome their non-participation. Transparency and ease-of-use also relate to the opportunity for third parties to maintain a direct relationship with their customers without interference of other parties. User databases have high value and therefore parties want to keep them in-house. Moreover, some services might require such direct relationship without involvement of other parties. Walled gardens, where the provider controls whom and what gets listed, can be unacceptable to some providers. The platform should cater to the needs of certain third party providers for a direct relationship in order to create an appealing offer to these third parties to step onto the platform. |
| Type | non-functional |
| Depends on | 7.1.1 - Use of Metadata for Multimedia Content organization 7.1.2 - Content Flow Organization |
| Child dependencies | 1.4.5 - Offering user-generated content over the SPICE platform 1.4.10 - Allow open access for multiple portals |
| Environment | |
| Other_info | |
| Category | open market;user;technical;device |
| Subcategory | content |
| Subcategory2 | content creation |
| Scenario_scene | unified.scene1 unified.scene2 |
| SPICE_value | service creation |
| Demo | |
| Keywords | service creation;ease-of-use;transparency;content creation |
| Home |