Profile cover photo
Profile photo
Martin Hepp
279 followers -
My main research interest is in using structured data inside Web content for articulating the value proposition of an enterprise or product.
My main research interest is in using structured data inside Web content for articulating the value proposition of an enterprise or product.

279 followers
About
Posts

Post has attachment
I remember that someone once shared a table or Google Doc document that traced schema.org types that were actively mentioned by at least one major search engine in its developer documentation, or otherwise known to matter. Unfortunately, I don't find the link - can anybody help? Maybe it was one of the many community contributions by +Aaron Bradley ;-)

Post has attachment
I recently observed that, in Google Webmaster Tools, it says that Googlebot detected schema:Article, schema:ImageObject, and schema:Book entities that are not marked up as such in the respective page content (neither via static HTML nor added to the DOM by active content).

To me this looks like Google is using parts of schema.org for representing data / meta-data produced by other Google software components heuristically.

Has anybody else observed a similar behavior?

Thanks!

Best wishes

Martin

Does anybody has in-depth experiences with Google's ability to process reverse properties in JSON-LD, as specified in

https://www.w3.org/TR/json-ld/#reverse-properties

?

Post has attachment
Wikidata Entity URIs

Hi all,
i just found that Wikidata itself states that the *identifiers* of entities are

http://www.wikidata.org/entity/<entityID>, like
http://www.wikidata.org/entity/Q76 for Barack Obama.

Quote from https://www.wikidata.org/wiki/Wikidata:Glossary#Identifiers_and_languages:

"Entity is the content of a Wikidata page, that either may be an item (in the main namespace), a property (in the property namespace). Every entity is uniquely identified by an entity ID, which is a prefixed number, for example starting with the prefix Q for an item and P for a property. An entity is also identified by a unique combination of label and description in each language. An entity may have alternate aliases in multiple languages. Each entity has also a dereferenceable URI that follows the pattern http://www.wikidata.org/entity/ID where ID is its entity ID."

Now, in practice, the official entity URIs first redirect via 301 to

https://www.wikidata.org/entity/Q76,

i.e. the HTTPS version (which is the official one anyway), and then via 303 to

https://www.wikidata.org/wiki/Special:EntityData/Q76

and then, likely via Content Negotiation (did not check) to

https://www.wikidata.org/wiki/Special:EntityData/Q76.json

I a browser, you end up with

https://www.wikidata.org/wiki/Q76

Now, in schema.org markup, which ones are the best to use for Semantic SEO, in particular for schema:sameAs?

In other cases, namely Google is fine with (or even prefers) Web page URIs, like ones Youtube account page etc.

What are your experiences? Did you observe any differences?

BTW, it is clear that from a purist Linked Data perspective, the entity identifiers are better, but I would like to know what is best for mainstream search engines.

Thanks!

Martin

Post has attachment
I am sure you have seen Google Tables:

https://research.google.com/tables

It seems to be mainly based on information extraction from tables in HTML.

Has anybody observed results that are extracted from schema.org markup in JSON-LD?

That would be a strong reason to add markup for multi-item pages.

The interesting thing with Google Tables is that I have seen some of the tables used in organic search results.

Post has attachment
We are doing a scientific study on improving schema.org skills in the developers community. If you are into schema.org development projects, please drop me an email to join: martin.hepp@unibw.de. Thanks!

Post has attachment
For some reason, the www.productontology.org service is now returning 404 errors for most (or all) entries. I am investigating the cause and will fix this, but it will take a few days. In the meantime, you can safely continue to use www.productontology.org types with the additionalType property in schema.org. The consumption of respective markup is unaffected by the problem with the human-readable pages in the Product Ontology service.

Post has shared content
An interesting next step in Google's strategy to cover an even bigger share of business transactions.
Interesting phenomena in Local Knowledge Panels for Professional Services

I noticed an interesting knowledge panel today in terms of bookings or “book now” options for professional services. A very cool display of orthopedic service offerings shows up when I select a procedure for an orthopedic surgeon. For want of more information, I would suspect that the structured display of service offerings may be coming from a third party service that is most likely zocdoc (I have not confirmed that, so any thoughts or info on that would be rather interesting)

In order to try and corroborate my theory, I also selected the viewmenu.com option which is displayed as a clickable link as an attribute for “products and services”. That link leads to data from another third party local data service provider, SinglePlatform (which I believe is also heavily leveraged by Facebook, amongst others) and the results are not consistent. (I guess those third party sources are not cross checked for “semantic consistency” – or … the mani pedi option for “hand problems” was pulled in as being related to the service offerings from the “Browse nearby option” – tho I suspect the former is the case).

Needless to say, I was impressed by the service offerings and detail level offered in the local panel for orthopedic services, but did find the fact that it appeared to imply that the most popular service offered by an orthopedic surgeon (specializing in sports injuries and many other types of “problems” , e.g. hip, foot, leg, knee etc - tho I would probably call foot pain a kind of "foot problem" .... a moot point and a bit nit picky here …) as being of the type "mani Pedi” for “hand problems” rather entertaining.

The notion of an orthopedic surgeon performing such a procedure just brought a smile to my face, albeit that may not have been the intent of the data displayed.

#knowledgePanel #localData #professionalServices
Photo
Add a comment...

Post has shared content
Dear all:

This just a brief update of the status of the automotive extension work in schema.org, the data standard for marking up car-related information for Google, Bing, Yahoo, Yandex, and others.

As many of you know, the first "core" extension has beend added to schema.org with the 2.0 release on May 12, 2015 (see http://schema.org/docs/releases.html).

This greatly enhanced the ability to publish car-related information to major search engines and other consumers of Web data.

Schema.org has now support for many standard car properties, like numberOfAirbags, numberOfAxles, numberOfForwardGears, fuelConsumption, fuelEfficiency vehicleEngine, EngineSpecification, etc.

For a full list of properties, see http://schema.org/Car.

Any proprietary properties can be added via http://schema.org/additionalProperty.

A few additional properties that we suggested to the sponsors of schema.org have gone into a so-called "schema.org extension" (for background, see https://schema.org/docs/extension.html).

Essentially, extensions hold properties and classes that are for a more specific subset of schema.org users. In practice, you can use the properties and classes from the extensions in the same manner as those from schema.org "core".

The extension is available at http://auto.schema.org/.

The extension is currently a final proposal undergoing a community review, see https://github.com/schemaorg/schemaorg/issues/704 for the respective discussion.

In general, the work on auto.schema.org is now coordinated in the W3C Automotive Ontology Community Group at https://www.w3.org/community/gao/. This is also the reason why this Google group has become a bit silent.

Please feel invited to join the W3C Community Group at https://www.w3.org/community/gao/ ("join this group"). Participation is free of charge and just requires a W3C account, which is also free.
Add a comment...

Post has attachment
Dear all:

This just a brief update of the status of the automotive extension work in schema.org, the data standard for marking up car-related information for Google, Bing, Yahoo, Yandex, and others.

As many of you know, the first "core" extension has beend added to schema.org with the 2.0 release on May 12, 2015 (see http://schema.org/docs/releases.html).

This greatly enhanced the ability to publish car-related information to major search engines and other consumers of Web data.

Schema.org has now support for many standard car properties, like numberOfAirbags, numberOfAxles, numberOfForwardGears, fuelConsumption, fuelEfficiency vehicleEngine, EngineSpecification, etc.

For a full list of properties, see http://schema.org/Car.

Any proprietary properties can be added via http://schema.org/additionalProperty.

A few additional properties that we suggested to the sponsors of schema.org have gone into a so-called "schema.org extension" (for background, see https://schema.org/docs/extension.html).

Essentially, extensions hold properties and classes that are for a more specific subset of schema.org users. In practice, you can use the properties and classes from the extensions in the same manner as those from schema.org "core".

The extension is available at http://auto.schema.org/.

The extension is currently a final proposal undergoing a community review, see https://github.com/schemaorg/schemaorg/issues/704 for the respective discussion.

In general, the work on auto.schema.org is now coordinated in the W3C Automotive Ontology Community Group at https://www.w3.org/community/gao/. This is also the reason why this Google group has become a bit silent.

Please feel invited to join the W3C Community Group at https://www.w3.org/community/gao/ ("join this group"). Participation is free of charge and just requires a W3C account, which is also free.
Wait while more posts are being loaded