3
  1. schema.org is better for SEO
  2. From https://lov.linkeddata.es/dataset/lov/ it seems FOAF has more adoption?

I have used the ontology:

@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix gr: <http://purl.org/goodrelations/v1#> .

GoodRelations is worry free as it is mostly compatible with schema.org, but what about the other two? i.e.

  1. dcterms:creator vs https://schema.org/creator
  2. foaf:Person vs https://schema.org/Person
Mzq
  • 1,796
  • 4
  • 30
  • 65
  • Regarding SEO: What you are probably referring to are the search result features search engines offer based on Schema.org, right? Note that search engines typically only support certain syntaxes: JSON-LD, Microdata, RDFa, but not Turtle. (See also: [Schema.org and SEO](https://webmasters.stackexchange.com/q/108333/17633)) – unor Feb 19 '19 at 07:45
  • Thanks for pointing that out. I think I can find converters to transform Turtle to all other formats, but if I defined it with other ontologies, I can't automatically convert it to the schema.org definitions, so should I change everything to use shema.org to save me trouble later on? – Mzq Feb 19 '19 at 09:48

1 Answers1

1

You can use multiple vocabularies/ontologies to describe the same entity.

If a consumer (like a search engine) only recognizes terms from a specific vocabulary (like Schema.org), it will simply ignore the terms from the other vocabularies (like FOAF).

So, for an entity that represents a person, you could use the types schema:Person, foaf:Person and/or dcterms:Agent. And for a book this person wrote, you could use the properties schema:creator, foaf:maker, and/or dcterms:creator.

If your primary motivation is SEO (instead of Linked Data), I would recommend to use the vocabulary Schema.org as far as possible, and other vocabularies in addition (at least where Schema.org is lacking, or, if you prefer, wherever it’s possible).

unor
  • 92,415
  • 26
  • 211
  • 360
  • So I can re-define original `foaf:homepage ` with https://schema.org/url, and keep both, so they can all be recognized? Or do I need to delete the other one if I decided to use schema.org? – Mzq Feb 19 '19 at 11:26
  • 1
    @Miranda: Pointing you to the first two sentences in my answer ;-) You can add as many triples as you want. There is no reason to assume that consumers would have a problem with triples they don’t need for the job they have. – unor Feb 19 '19 at 12:30