• US$410

• 53 diseños

• 8 diseñadores

---

Resumen de Diseño de Logo

My company, RepreZen, is starting an open source initiative that will have three related modules:

1. RAPID-ML is a language for API modeling. API means Application Programming Interface, which a back-end software "service" provides to client applications (mobile, web, etc.) so those applications can access data or functionality provided by the service. RAPID-ML is a text-based, structured modeling language.

2. RAPID-Schema is a language that describes data models, and adapts data models to APIs. We refer to this adaptation process as "realization". Realizing a data model involves choosing a subset of data model properties that the API is concerned with, applying constraints, and choose whether to embed or link to related data.

You can see realization modeling here:
https://www.youtube.com/watch?v=7F-EooNc9Q0

3. RAPID-View is a specification for graphical presentation of an API, with its associated data model. You can see RAPID-View diagrams in the video above, and you can play with an interactive RAPID-View diagram here:

https://goo.gl/d6Op2N

All three of these specifications have the RAPID prefix. RAPID stands for Resource API Definition.

We need three logos that are closely related to each other, but distinct. Ideally, there should be a "base logo" for the RAPID family, and an overlay or adornment -- an additional graphic element -- for each of the three specifications.

Also, the RAPID logo family should complement RepreZen's logo and company image. You can see our site at http://www.reprezen.com, and I will attach logos to this project description. The RAPID logos should be distinct from the RepreZen logo, so as not to confuse the two. But they should complement each other.

Note: The RepreZen logo uses the Neuropolitical font. The RAPID logos can use this, or another font; it's up to the designer.

Each logo should have a graphical element and a text element. It helps if the graphic element is self-standing, so it can be used without the text element. And it helps if the graphic element is close to being square in its aspect ratio -- not too much difference between the height and width.

There are at least three other well-known specifications for API design languages. It is important that the RAPID family logos are visually different from those:
http://swagger.io/
http://raml.org/
https://apiblueprint.org/

Objetivo del mercado(s)

Software developers and IT managers.

Tipo de industria / entidad

It Company

Texto del logo

RAPID-ML, RAPID-Schema, and RAPID-View (see project description)

---

Estilos de logo de interés

---

Estilos de fuente para usar

---

Mira y siente

Cada control deslizante ilustra las características de la marca del cliente y el estilo que debe comunicar el diseño de tu logotipo.

---

Requisitos

Debes tener

• On acceptance, all source files must be provided (AI, PSD, etc.).
• Must have a style that is modern, distinctive, classy and powerful.
• The graphic images must be simple enough that they can scale down to icon size (with minimal modification), and still be recognizable.
• One of the central challenges is to find a good visual representation of these abstract concepts: API (for RAPID-ML), Data Model (for RAPID-Schema), and Diagram (for RAPID-View).
• RAPID-View
• ==========
• RAPID-View is the easiest, becasue the diagram itself is visual. (See the interactive diagram at https://goo.gl/d6Op2N.) This suggest some ideas for a simplified, stylized graphical element that represents an API diagram in our RAPID-View logo.
• RAPID-Schema
• ============
• RAPID-Schema is a bit more difficult. Data models are often represented as Entity-Relationship diagrams (https://goo.gl/msP7zZ) or UML Class diagrams (https://goo.gl/0AeeO6), but these are too close to the RAPID-View diagram visualization.
• Some ideas:
• 1. Data models for APIs are often written in languages like XML Schema or JSON Schema. These are tree-structured, so it's common to see icons for these schemas that use variations on the idea of hierarchy, outline, or tree. (https://goo.gl/v48BZr , https://goo.gl/t25Hx4 )
• (Note: XML uses angle brackets and slashes, so you'll see some icons with as a symbol for XML or XML Schema. Best to avoid this, because XML is out of style now. JSON schemas use curly braces. This is better, and more modern, but also used in the Swagger icon, which we don't want to duplicate. Best to avoid any use of ASCII characters in the logos.)
• 2. Data is often represented as a table or grid (https://goo.gl/22TVue)
• 3. RAPID-Schema describes the structure of data that travels in "messages" between the API and the client. Messages can be represented as an envelope (https://goo.gl/2gLllR) or a document (https://goo.gl/zU7HNO).
• So, taking some of the above ideas, you might be able to convey the idea of a schema, or data model, that defines the format of tree-structured data, traveling in messages. Or something like that. ;-) This is a complex and abstract concept, but we need to keep the logo image simple. See what you can come up with!
• RAPID-ML
• ========
• This is probably the most abstract concept of the three. RAPID-ML is a language to describe an API. An API is an Application Programming Interface that provides data or functionality to client applications.
• Think of it as a web URL that gives you back structured data instead of a web page. In fact, some APIs work exactly like this -- they are read-only APIs used to get some kind of data. Other APIs require that you pass structured data to the URL, and these may do something significant with that data, such as store it in a database, place an order, or charge a credit card.
• Some ideas for visual representation:
• 1. This is an API conceptual diagram that we developed for our old website: https://www.dropbox.com/s/ic98vzkmwnmgzw0/img-REST%402x.jpg?dl=0
• The shapes represent "resources" (normally identified by URIs.) The sockets have four pins, each representing one of the four most common HTTP verbs: GET, PUT, POST, and DELETE.
• The TV screen represents a client application or web browser, showing a resource that it's currently "plugged into". The resource shown on the screen has connections to other shapes, representing hyperlinks.
• 2. APIs are kind of like plugs, so you often see this representation in icons: https://goo.gl/YFtv4f
• 3. UML uses a stylized "ball and socket" notation to represent the interface provider (ball) and consumer (socket). https://goo.gl/dlOIwl
• 4. APIs are often hosted in the cloud, so you often see clouds in API icons.
• 5. APIs encapsulate some kind of process, so it's common to see gear icons. https://goo.gl/Rz2kmK

---

Archivos

Descargar todos los archivos - 0,1 MB