- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Mon, 26 Apr 2021 10:55:49 -0400
- To: public-credentials@w3.org
On 4/26/21 10:26 AM, Nikos Fotiou wrote: >> those values should be: >> >> http://www.w3.org/2001/XMLSchema#date > So why this, and not e.g., https://schema.org/Date? The short answer is "history and precedence". There are many more systems on the planet today that understand `http://www.w3.org/2001/XMLSchema#date` than `https://schema.org/Date`... mostly because the former has existed for 20 years, and the latter has only existed for 10 years (and is targeted at search engine optimization). The former is used across healthcare, government, a TON of systems that are powered by XML (retail, banking, etc.), while the latter is mostly for SEO and is mainly used at Google, Bing, and Apple. This is where things start transitioning towards "art" from "hard science". There is no hard rule on this... Tobias could have used `Date`... the value space is the same, but I expect he chose to use `XMLSchema#date` because of the larger body of software systems that understand the property. I think it's the right call... at the end of the day, we just need to use a URL to identify the concept of a "date". One could even argue that `schema.org/Date` and `XMLSchema#date` are semantically equivalent (they are, and they have the same value space, IIRC). We could add reasoning statements into our software to detect both as equivalent, but that would add complexity to software... so, we try to not do that and just use the URL that people have been using to represent ISO-8601 dates for 20+ years now. -- manu -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. blog: Veres One Decentralized Identifier Blockchain Launches https://tinyurl.com/veres-one-launches
Received on Monday, 26 April 2021 14:56:05 UTC