Dan Brickley comments

Results 577 comments of


                                            Dan Brickley

cleanup Physician per #806 to clarify that a physician is not a place, adding /usNPI identifiers

see https://github.com/schemaorg/schemaorg/pull/3427#issuecomment-1869470667 for a concrete proposal

cleanup Physician per #806 to clarify that a physician is not a place, adding /usNPI identifiers

in https://github.com/schemaorg/schemaorg/pull/3427 @jvandriel suggests making Physician a subtype of Occupation to benefit from https://schema.org/occupationalCategory. I am wary of the former as we could end up in a situation like Product...

cleanup Physician per #806 to clarify that a physician is not a place, adding /usNPI identifiers

Thanks for investigating! 1. Ok, let's investigate Dentist and Optician but I would prefer to proceed with those as a followup activity rather than scope-creeping this issue. I'll open a...

cleanup Physician per #806 to clarify that a physician is not a place, adding /usNPI identifiers

OK the PR is merged. Thanks, everyone!

Description of :source meta property missing

It was originally a mistake we (ok, I) made in 2013, adding large medical vocab with weak usecases whose term names were in several cases too general. https://web.archive.org/web/20130916055030/http://schema.org/source Having nothing...

Description of :source meta property missing

I was suggesting that we could have a source property, with isBasedOn being a subproperty that is slightly more specific, and that our definition would explicitly to some extent defer...

Example IDs (data/ext/..) conflicts with new example IDs in data/examples.txt

@RichardWallis can you comment? My understanding was that `./software/util/buildsite.py --release` ought to clean up IDs (adding where necessary at least) when building the site.

Adding DefinedTerm as range for properties expecting also a URL or PropertyValue or Text (if it corresponds to a standard)

While I am wary of adding DefinedTerm indiscriminately across all of schema.org, it does make sense at least for measurementTechnique. Any others that are high priority to folks here?

Adding DefinedTerm as range for properties expecting also a URL or PropertyValue or Text (if it corresponds to a standard)

Done! This is in release 19.0, just pushed to the live site.

Adding DefinedTerm as range for properties expecting also a URL or PropertyValue or Text (if it corresponds to a standard)

Nearby (and still needing attention), https://github.com/schemaorg/schemaorg/issues/3125