Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add HealthTopicContent, subtype of WebContent, plus an enumeration indicating topical aspects #2374

Open
danbri opened this issue Oct 22, 2019 · 6 comments
Assignees

Comments

@danbri
Copy link
Contributor

@danbri danbri commented Oct 22, 2019

Building on proposed WebContent (see #2358):

A type HealthTopicContent, which is URL-addressable web content (whether a site, web page, or part of a web page) that ... holds content about an aspect of a health topic. This may be comprised of several parts or sections and use different types of media. Instances of WebContent (and hence HealthTopicContent) can be related using hasPart / isPartOf where there is some kind of content hierarchy, and their content indicated with "about" and "mentions" e.g. building upon our existing https://schema.org/MedicalCondition vocabulary.

In addition, I propose an enumeration of the different topical aspects found in such content, as well as a property associating WebContent instances with those identified aspects.

Specifics will be given in schema definitions for review.

@danbri danbri self-assigned this Oct 22, 2019
danbri added a commit that referenced this issue Oct 22, 2019
@danbri

This comment has been minimized.

Copy link
Contributor Author

@danbri danbri commented Oct 22, 2019

We could also note http://schema.org/MedicalWebPage as a subtype of HealthTopicContent

@danbri

This comment has been minimized.

Copy link
Contributor Author

@danbri danbri commented Oct 22, 2019

I've posted a draft for review in the pending section:

http://webschemas.org/WebContent

http://webschemas.org/HealthTopicContent
Thing > CreativeWork > WebContent > HealthTopicContent
HealthTopicContent is WebContent that is about some aspect of a health topic, e.g. a condition, its symptoms or treatments. Such content may be comprised of several parts or sections and use different types of media. Multiple instances of WebContent (and hence HealthTopicContent) can be related using hasPart / isPartOf where there is some kind of content hierarchy, and their content described with about and mentions e.g. building upon the existing MedicalCondition vocabulary.

http://webschemas.org/hasHealthAspect
Indicates the aspect or aspects specifically addressed in some HealthTopicContent. For example, that the content is an overview, or that it talks about treatment, self-care, treatments or their side-effects.

http://webschemas.org/HealthAspectEnumeration
HealthAspectEnumeration enumerates several aspects of health content online, each of which might described using hasHealthAspect and HealthTopicContent.

http://webschemas.org/BenefitsAspect
Content about the benefits and advantages of usage or utilization of topic.

etc

@jvandriel

This comment has been minimized.

Copy link

@jvandriel jvandriel commented Oct 22, 2019

To be honest, I feel several brain freezes coming up based on how does this relate to the medical extention:

(a) Will this proposal in any form have any relations to types specified in the extention?

(b) Having done quite some markup for medical organizations I'm wondering if the properties/Enumerations are intended to be used for web pages (and their topics) as well? (which in my mind instantly because hugely confusing and bloated)

@jvandriel

This comment has been minimized.

Copy link

@jvandriel jvandriel commented Oct 22, 2019

Oh, and if I remember discussions around the medical extention correctly, types and properties making any beneficial claims were purposely avoided due to such claims being impossible to verify.

Expectations were that if introduced such types and properties would more often than not contain false claims than medically have no ground.

danbri added a commit that referenced this issue Oct 22, 2019
@twamarc

This comment has been minimized.

Copy link
Contributor

@twamarc twamarc commented Oct 23, 2019

for me it's fine as far as the intention is purerly to describe the web content.
@danbri: can you maybe fix the property name from webschemas.org/hasHealthHealthAspect to http://webschemas.org/hasHealthAspect ? Also to harmonize in other properties by replacing double HealthHealth by Health? (eg . in SelfCareHealthHealthAspect, etc)

@danbri

This comment has been minimized.

Copy link
Contributor Author

@danbri danbri commented Oct 23, 2019

Hi @twamarc @jvandriel - you found this before I had a chance to forward it around!

First: the "HealthHealth" thing was simply an editorial error - it should be fixed already.

As far as the relationship goes to our existing large set of medically-oriented terms i.e. https://health-lifesci.schema.org/ - as @twamarc notes the emphasis here is on Web information. We are still in a situation where the medical terms are a large % of schema.org's vocabulary but relatively under-exploited in terms of products/services/features making explicit use of them. My hope is that HealthTopicContent will help us find a few more practical and visible usecases for https://schema.org/MedicalCondition and nearby.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.