Difference between revisions of "Schema.org"
| Line 1: | Line 1: | ||
Schema.org is an initiative sponsored by Google, Microsoft, Yahoo and Yandex that promotes a very pragmatic approach to the semantic web/linked data. | Schema.org is an initiative sponsored by Google, Microsoft, Yahoo and Yandex that promotes a very pragmatic approach to the semantic web/linked data. | ||
| + | the Schema.org vocabulary is recognized the search engines listed above. | ||
At the time of writing over 10 million sites use Schema.org to markup content, and many applications of the involved companies (e.g., GMail, Google Calendar) exploit Schema.org metadata to provide added value features (e.g., automatically interpreting reservation details to add events to your calendar). | At the time of writing over 10 million sites use Schema.org to markup content, and many applications of the involved companies (e.g., GMail, Google Calendar) exploit Schema.org metadata to provide added value features (e.g., automatically interpreting reservation details to add events to your calendar). | ||
| Line 7: | Line 8: | ||
The [http://schema.org/docs/full.html Schema.org ontology] has, at the time of writing, relatively little support for software-related entities, most notably: | The [http://schema.org/docs/full.html Schema.org ontology] has, at the time of writing, relatively little support for software-related entities, most notably: | ||
| − | * [http://schema.org/Code Code] | + | * [http://schema.org/Code Code] |
* [http://schema.org/SoftwareApplication SoftwareApplication] | * [http://schema.org/SoftwareApplication SoftwareApplication] | ||
| + | ** MobileApplication | ||
| + | ** WebApplication | ||
* [http://schema.org/SoftwareSourceCode SoftwareSourceCode] | * [http://schema.org/SoftwareSourceCode SoftwareSourceCode] | ||
| + | |||
| + | The hierarchical organization of schema.org show that all three are subclasses of ''CreativeWork'' which is a subclass of ''Thing''. | ||
| + | ''SoftwareApplication'' and ''SoftwareSourceCode'' are subclasses of code; ''MobileApplication'' and ''WebApplication'' are subclasses of ''SoftwareApplication''. | ||
| + | |||
| + | === Properties === | ||
| + | ===== Properties common to ''Code'', ''SoftwareApplication'' and ''SoftwareSourceCode'' ===== | ||
| + | <code>'about', 'accessibilityAPI', 'accessibilityControl', 'accessibilityFeature', 'accessibilityHazard', 'accountablePerson', 'additionalType', 'aggregateRating', 'alternateName', 'alternativeHeadline', 'associatedMedia', 'audience', 'audio', 'author', 'award', 'character', 'citation', 'comment', 'commentCount', 'contentLocation', 'contentRating', 'contributor', 'copyrightHolder', 'copyrightYear', 'creator', 'dateCreated', 'dateModified', 'datePublished', 'description', 'disambiguatingDescription', 'discussionUrl', 'editor', 'educationalAlignment', 'educationalUse', 'encoding', 'exampleOfWork', 'fileFormat', 'funder', 'genre', 'hasPart', 'headline', 'image', 'inLanguage', 'interactionStatistic', 'interactivityType', 'isAccessibleForFree', 'isBasedOn', 'isFamilyFriendly', 'isPartOf', 'keywords', 'learningResourceType', 'license', 'locationCreated', 'mainEntity', 'mainEntityOfPage', 'mentions', 'name', 'offers', 'position', 'potentialAction', 'producer', 'provider', 'publication', 'publisher', 'publishingPrinciples', 'recordedAt', 'releasedEvent', 'review', 'sameAs', 'schemaVersion', 'sourceOrganization', 'spatialCoverage', 'sponsor', 'temporalCoverage', 'text', 'thumbnailUrl', 'timeRequired', 'translator', 'typicalAgeRange', 'url', 'version', 'video', 'workExample' </code> | ||
| + | We noted that the propreties in ''Code'' are a subset to ''SoftwareApplication'' and ''SoftwareSourceCode''. | ||
| + | |||
| + | ===== Properties common to ''SoftwareSourceCode'' and ''SoftwareApplication'' ===== | ||
| + | <code> 'targetProduct' </code> | ||
| + | |||
| + | ===== Properties only in ''SoftwareApplication'' ===== | ||
| + | <code> 'installUrl', 'memoryRequirements', 'processorRequirements', 'countriesSupported', 'featureList', 'availableOnDevice', 'applicationSubCategory', 'interactionService', 'applicationSuite', 'softwareHelp', 'countriesNotSupported', 'actionApplication', 'applicationCategory', 'softwareRequirements', 'screenshot', 'releaseNotes', 'softwareAddOn', 'storageRequirements', 'fileSize', 'permissions', 'downloadUrl', 'softwareVersion', 'supportingData', 'operatingSystem' </code> | ||
| + | |||
| + | ===== Properties only in ''SoftwareSourceCode'' ===== | ||
| + | <code> 'codeRepository', 'runtimePlatform', 'codeSampleType', 'programmingLanguage' </code> | ||
| + | |||
| + | |||
| + | == Websites and formats using schema.org == | ||
| + | The usage of schema.org classes when testing web pages with the [https://search.google.com/structured-data/testing-tool/u/0/ google's structured data testing tool] where software projects, applications or code are presented: | ||
| + | === Code === | ||
| + | * [http://zenodo.org/ Zenodo] | ||
| + | === SoftwareApplication === | ||
| + | * [http://sourceforge.net/ SourceForge] uses also DOAP on Projects | ||
| + | |||
| + | === SoftwareSourceCode === | ||
| + | * [http://github.com/ Github] | ||
| + | * CodeMeta initiative uses schema.org classes for Person and for SoftwareSourceCode in a Json-ld format | ||
| + | |||
| + | |||
| + | == Linked Data and schema.org == | ||
| + | schema.org vocabulary can be used on a website page to link data with an appropriate syntax (Microdata, RDFa or JSON-LD). A short getting started article is available on [http://schema.org/docs/gs.html schema.org]. | ||
| + | |||
| + | Using schema.org enables rich search results on various search engines like Google or Yahoo, listing in Google's knowledge graph and other possibilities with structured data.[https://yoast.com/structured-data-schema-ultimate-guide/] | ||
| + | |||
| + | For the Software Heritage user inerface a markup syntax and vocabulary are yet to be decided. | ||
== References == | == References == | ||
| − | |||
* [http://schema.org/ homepage] | * [http://schema.org/ homepage] | ||
* [http://schema.org/docs/full.html full hierarchy], i.e., schema.org ontology | * [http://schema.org/docs/full.html full hierarchy], i.e., schema.org ontology | ||
| + | * [http://en.wikipedia.org/wiki/Schema.org schema.org on Wikipedia] | ||
| + | |||
| + | [[Category:Related work]] | ||
| + | [[Category:Software metadata]] | ||
| + | [[Category:Software ontology]] | ||
| + | |||
[[Category:Related work]] | [[Category:Related work]] | ||
[[Category:Related initiative]] | [[Category:Related initiative]] | ||
[[Category:Software ontology]] | [[Category:Software ontology]] | ||
Latest revision as of 15:07, 25 April 2017
Schema.org is an initiative sponsored by Google, Microsoft, Yahoo and Yandex that promotes a very pragmatic approach to the semantic web/linked data. the Schema.org vocabulary is recognized the search engines listed above.
At the time of writing over 10 million sites use Schema.org to markup content, and many applications of the involved companies (e.g., GMail, Google Calendar) exploit Schema.org metadata to provide added value features (e.g., automatically interpreting reservation details to add events to your calendar).
Ontology
The Schema.org ontology has, at the time of writing, relatively little support for software-related entities, most notably:
- Code
- SoftwareApplication
- MobileApplication
- WebApplication
- SoftwareSourceCode
The hierarchical organization of schema.org show that all three are subclasses of CreativeWork which is a subclass of Thing. SoftwareApplication and SoftwareSourceCode are subclasses of code; MobileApplication and WebApplication are subclasses of SoftwareApplication.
Properties
Properties common to Code, SoftwareApplication and SoftwareSourceCode
'about', 'accessibilityAPI', 'accessibilityControl', 'accessibilityFeature', 'accessibilityHazard', 'accountablePerson', 'additionalType', 'aggregateRating', 'alternateName', 'alternativeHeadline', 'associatedMedia', 'audience', 'audio', 'author', 'award', 'character', 'citation', 'comment', 'commentCount', 'contentLocation', 'contentRating', 'contributor', 'copyrightHolder', 'copyrightYear', 'creator', 'dateCreated', 'dateModified', 'datePublished', 'description', 'disambiguatingDescription', 'discussionUrl', 'editor', 'educationalAlignment', 'educationalUse', 'encoding', 'exampleOfWork', 'fileFormat', 'funder', 'genre', 'hasPart', 'headline', 'image', 'inLanguage', 'interactionStatistic', 'interactivityType', 'isAccessibleForFree', 'isBasedOn', 'isFamilyFriendly', 'isPartOf', 'keywords', 'learningResourceType', 'license', 'locationCreated', 'mainEntity', 'mainEntityOfPage', 'mentions', 'name', 'offers', 'position', 'potentialAction', 'producer', 'provider', 'publication', 'publisher', 'publishingPrinciples', 'recordedAt', 'releasedEvent', 'review', 'sameAs', 'schemaVersion', 'sourceOrganization', 'spatialCoverage', 'sponsor', 'temporalCoverage', 'text', 'thumbnailUrl', 'timeRequired', 'translator', 'typicalAgeRange', 'url', 'version', 'video', 'workExample'
We noted that the propreties in Code are a subset to SoftwareApplication and SoftwareSourceCode.
Properties common to SoftwareSourceCode and SoftwareApplication
'targetProduct'
Properties only in SoftwareApplication
'installUrl', 'memoryRequirements', 'processorRequirements', 'countriesSupported', 'featureList', 'availableOnDevice', 'applicationSubCategory', 'interactionService', 'applicationSuite', 'softwareHelp', 'countriesNotSupported', 'actionApplication', 'applicationCategory', 'softwareRequirements', 'screenshot', 'releaseNotes', 'softwareAddOn', 'storageRequirements', 'fileSize', 'permissions', 'downloadUrl', 'softwareVersion', 'supportingData', 'operatingSystem'
Properties only in SoftwareSourceCode
'codeRepository', 'runtimePlatform', 'codeSampleType', 'programmingLanguage'
Websites and formats using schema.org
The usage of schema.org classes when testing web pages with the google's structured data testing tool where software projects, applications or code are presented:
Code
SoftwareApplication
- SourceForge uses also DOAP on Projects
SoftwareSourceCode
- Github
- CodeMeta initiative uses schema.org classes for Person and for SoftwareSourceCode in a Json-ld format
Linked Data and schema.org
schema.org vocabulary can be used on a website page to link data with an appropriate syntax (Microdata, RDFa or JSON-LD). A short getting started article is available on schema.org.
Using schema.org enables rich search results on various search engines like Google or Yahoo, listing in Google's knowledge graph and other possibilities with structured data.[1]
For the Software Heritage user inerface a markup syntax and vocabulary are yet to be decided.
References
- homepage
- full hierarchy, i.e., schema.org ontology
- schema.org on Wikipedia