El coordinador de los diputados de Morena Jos Mara Martnez (Chema) realiz una gira por los municipios Tlaquepaque, Guadalajara, Zapopan, Ciudad Guzmn y Puerto Vallarta para protestar por las #PinchesRentasCaras en Jalisco y favorecer a las mujeres en sus salarios.
Martinez Martinez visit los municipios sealados para recabar las inquietudes de las personas que todos los das trabajan y no puede acceder a una viviendas digna por sus altos costos, al cuestionar a las personas "Chema" escucho como la mayora de estas coinciden en que el actual salario no alcanza para rentar o comprar una vivienda en una zona con todos los servicios.
"Desde aqu poder construir una poltica pblica que desde el congreso garantice la vivienda digna para todos los jaliscienses buscando que se ajuste al ingreso promedio de cualquier licencia pero tambin con perspectiva de gnero" seal Jos Mara Martnez.
Chema Martinez dijo que en Jalisco existe una brecha salarial muy marcada entre hombre y mujeres la cual genera desigualdad e injusticia ya que en promedio un hombre gana un 25 por ciento ms que una mujer y eso dificulta que ests puedan contar con un proyecto de vida a travs de rentas caras.
Por lo anterior el legislador indic que adems de promover la poltica pblica de vivienda digna tambin abordar otra poltica que garantice vivienda digna con perspectiva de gnero para que las mujeres tengan la oportunidad de acceder a ellas y adems contar con salarios adecuados a sus necesidades.
Con sus iniciativas Martnez Martnez busca favorecer a los grupos vulnerables del estado ya que la economa salarial no est acord a la del mundo inmobiliario dnde slo el que goza de gran poder adquisitivo puede acceder a viviendas de calidad y con todos los servicios bsicos.
La activacin que realiz Chema en los diferentes municipios cosisti en recaudar firmas de apoyo a la iniciativa de #PinchesRentasCaras, hablar sobre los contras de ir a vivir a las orillas de las ciudad porque son baratas y la defensa y fortalecimiento de las mujeres, la gira continuar en prximos das pues tiene la intencin de recorrer todo el estado.
As schema.org has grown, we have explored various mechanisms for community extension as a way of adding more detailed descriptive vocabulary that builds on the schema.org core. Some areas of Schema.org were developed as "named extensions", and have dedicated entry pages. We previously called these "hosted" extensions, but they are best considered simply as views into a single collection of schema definitions.
For example, via the auto section there is a property for emissionsCO2,and via the bib section we have a property publisherImprint.However, from the perspective of a publisher, these are simply schema.org properties.
Google Search works hard to understand the content of a page. You can help us by providing explicit clues about the meaning of a page to Google by including structured data on the page. Structured data is a standardized format for providing information about a page and classifying the page content; for example, on a recipe page, what are the ingredients, the cooking time and temperature, the calories, and so on.
Adding structured data can enable search results that are more engaging to users and might encourage them to interact more with your website, which are called rich results. Here are some case studies of websites that have implemented structured data for their site:
Google uses structured data that it finds on the web to understand the content of the page, as well as to gather information about the web and the world in general, such as information about the people, books, or companies that are included in the markup. For example, here is a JSON-LD structured data snippet that might appear on a recipe page, describing the title of the recipe, the author of the recipe, and other details:
Google Search also uses structured data to enable special search result features and enhancements. For example, a recipe page with valid structured data is eligible to appear in a graphical search result, as shown here:
Structured data is coded using in-page markup on the page that the information applies to. The structured data on the page describes the content of that page. Don't create blank or empty pages just to hold structured data, and don't add structured data about information that is not visible to the user, even if the information is accurate. For more technical and quality guidelines, see the Structured data general guidelines.
This documentation describes which properties are required, recommended, or optional for structured data with special meaning to Google Search. Most Search structured data uses schema.org vocabulary, but you should rely on the Google Search Central documentation as definitive for Google Search behavior, rather than the schema.org documentation. There are more attributes and objects on schema.org that aren't required by Google Search; they may be useful for other search engines, services, tools, and platforms.
Be sure to check your structured data using the Rich Results Test during development, and the Rich result status reports after deployment, to monitor the validity of your pages, which might break after deployment due to templating or serving issues.
You must include all the required properties for an object to be eligible for appearance in Google Search with enhanced display. In general, defining more recommended features can make it more likely that your information can appear in Search results with enhanced display. However, it is more important to supply fewer but complete and accurate recommended properties rather than trying to provide every possible recommended property with less complete, badly-formed, or inaccurate data.
In addition to the properties and objects documented here, Google can make general use of the sameAs property and other schema.org structured data. Some of these elements may be used to enable future Search features, if they are deemed useful.
Google Search supports structured data in the following formats, unless documented otherwise. In general, we recommend using a format that's easiest for you to implement and maintain (in most cases, that's JSON-LD); all 3 formats are equally fine for Google, as long as the markup is valid and properly implemented per the feature's documentation.
Be sure to follow the general structured data guidelines, as well as any guidelines specific to your structured data type; otherwise your structured data might be ineligible for rich result display in Google Search.
Once you're comfortable with the basics of structured data, explore the list of structured data features in Google Search and pick a feature to implement. Each guide goes into detail on how to implement the structured data in a way that makes your site eligible for a rich result appearance on Google Search.
You probably want to compare performance of your pages with structured data with those pages that don't have structured data, in order to decide if it's worth your effort. The best way to do that is to run a before and after test on a few pages on your site. This can be a little tricky, since page views can vary for a single page for various reasons.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Jajaja Que comentarios graciosos.
Respondindo a tu pregunta Chema..a ver... "Chema Alonso novia" se busca x varias razones. Podrian ser: Para saber si tienen chances sentimentales contigo, hackear a tu novia, hackearte mediante tu novia, simple curiosidad de fans, u otras razones.
Tienes muchos fans,estas super guapo y algunos podrian tener inters en hackearte, as que podran ser estas u otras razones ms.
PD: Por cierto Chema, tienes novia? XD