Dan Brickley

Thad - on what evidence do you say that? On Sun, 26 Aug 2018, 02:42 Thad Guidry, wrote: > ALL - Software Types are already recognized by most search engines...

How about broadening http://schema.org/sponsor and also adding funder as a subproperty?

see also https://github.com/CrossRef/open-funder-registry/issues/5

- http://schema.org/character "Fictional person connected with a creative work." - http://schema.org/Person is "A person (alive, dead, undead, or fictional)." We don't explicitly tie "Person" to human, although humans would obviously...

@philarcher suggests that ```^https?:(\/\/((([^\/?#])@)?([^\/?#:])(:([^\/?#]))?))?([^?#])(((\/01\/)((\d{8}|\d{12}|\d{13}|\d{14})[^\/]+)(\/[^/]+\/[^/]+)?[/]?(\?([^?\n]))?(#([^\n]))?))``` Is what most will need for GTIN extraction. Given the complexity I am wary of putting it in the spec as-is, but for now will point...

@philarcher @alex-jansen can you take a look at this. Raw schema file is https://raw.githubusercontent.com/schemaorg/schemaorg/main/data/ext/pending/issue-1244.ttl I will proceed towards staging but welcome your early review! (and anyone else's...)

I should add that the definition already encourages GTINs as URLs in the textual part, which is why things are currently confusing and inconsistent.

Thanks @philarcher ! Would it make sense to nudge the path part of the URL towards using [.well-known](https://www.ietf.org/rfc/rfc5785.txt) ? I appreciate the spec is already mostly baked, though...

@philarcher yes - I understand those tradeoffs! But given the existence of /.well-known/ why not at least register a path name for that, so that those who want to use...

I would encourage you to try to find an idiom that re-uses existing schema.org terms (e.g. Person, Organization, https://schema.org/DigitalDocument, https://schema.org/encodingFormat ...). There is so much churn and chaos in the...