3 ms·

And then there is https://schema.org/ https://schema.org/ It's the item* attributes, e.g.: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_at

by panzi 4mo ago

And then there is https://schema.org/ https://schema.org/ It's the item* attributes, e.g.: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/itemprop https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/... Also Dublin Core in <meta> tags. Why do they keep adding conflicting meta data formats to HTML!?!

9dev 4mo ago
https://xkcd.com/927/ https://xkcd.com/927/
captn3m0 4mo ago
There is also microformats.
klodolph 4mo ago
I think if you are using Dublin Core, it’s because you’re a library. Maybe I am off the mark, but that is the sense I get from this—not all these standards should be used for all pages on the web. I think you should just think about what metadata you actually care about, and the main metadata I care about (choose your own list) is authorship, publish date, last update, subject keywords, thumbnail (OpenGraph 1200x630), and summary. There’s a long list of additional metadata that I could put in my webpages because there are standardized ways to do it, but, why bother?
- rhdunn 4mo ago
  Dublin Core is effectively similar/related to schema.org's CreativeWork. If you have a creative work (audiobook, short story, news article, etc.) then Dublin Core is applicable, in addition to the corresponding CreativeWork subtype. And yes, you should use whatever metadata is applicable to your site and test it against the search engines/etc. you want to support to make sure that they are reading the metadata correctly.
jauco 4mo ago
To be fair schema.org and dublin core say “when a property is name ‘title’ it means …” and you can expect to find the following properties… Json-ld says: if you want to know whether the “title” property means the schema.org or the dublin core variant then you can find out which it is by <json-ld algorithm> So you’d always use json-ld _with_ schema.org or something.
alwillis 4mo ago
They don't conflict; they were designed to work together. You can have schema.org (in JSON-LD, RDFa, or micro data) on the same page as Dublin Core, etc. For example, there's no explicit property in schema's Person type [1] for a nickname. But the FOAF standard does [2]. Just add FOAF to the JSON-LD context: { "@context": { "@vocab": "https://schema.org/", "foaf": "http://xmlns.com/foaf/0.1/", "pronouns": "https://schema.org/pronouns" } You now use the FOAF nickname property: "@type": "Person", "givenName": "Timothy", "familyName": "Berners-Lee", "foaf:nick": "TBL", You can do the same thing with Dublin Core, DBPedia, etc. [1]: https://schema.org/Person https://schema.org/Person [2]: https://xmlns.com/foaf/spec/#term_nick https://xmlns.com/foaf/spec/#term_nick

by panzi 4mo ago

9dev 4mo ago

https://xkcd.com/927/ https://xkcd.com/927/

captn3m0 4mo ago

There is also microformats.

klodolph 4mo ago

I think if you are using Dublin Core, it’s because you’re a library. Maybe I am off the mark, but that is the sense I get from this—not all these standards should be used for all pages on the web. I think you should just think about what metadata you actually care about, and the main metadata I care about (choose your own list) is authorship, publish date, last update, subject keywords, thumbnail (OpenGraph 1200x630), and summary. There’s a long list of additional metadata that I could put in my webpages because there are standardized ways to do it, but, why bother?

rhdunn 4mo ago
Dublin Core is effectively similar/related to schema.org's CreativeWork. If you have a creative work (audiobook, short story, news article, etc.) then Dublin Core is applicable, in addition to the corresponding CreativeWork subtype. And yes, you should use whatever metadata is applicable to your site and test it against the search engines/etc. you want to support to make sure that they are reading the metadata correctly.

jauco 4mo ago

To be fair schema.org and dublin core say “when a property is name ‘title’ it means …” and you can expect to find the following properties… Json-ld says: if you want to know whether the “title” property means the schema.org or the dublin core variant then you can find out which it is by <json-ld algorithm> So you’d always use json-ld _with_ schema.org or something.

alwillis 4mo ago

They don't conflict; they were designed to work together. You can have schema.org (in JSON-LD, RDFa, or micro data) on the same page as Dublin Core, etc. For example, there's no explicit property in schema's Person type [1] for a nickname. But the FOAF standard does [2]. Just add FOAF to the JSON-LD context: { "@context": { "@vocab": "https://schema.org/", "foaf": "http://xmlns.com/foaf/0.1/", "pronouns": "https://schema.org/pronouns" } You now use the FOAF nickname property: "@type": "Person", "givenName": "Timothy", "familyName": "Berners-Lee", "foaf:nick": "TBL", You can do the same thing with Dublin Core, DBPedia, etc. [1]: https://schema.org/Person https://schema.org/Person [2]: https://xmlns.com/foaf/spec/#term_nick https://xmlns.com/foaf/spec/#term_nick