W3C home > Mailing lists > Public > public-schemaorg@w3.org > December 2016

Re: Extension proposal for Senior Housing

From: Thad Guidry <thadguidry@gmail.com>
Date: Wed, 21 Dec 2016 02:31:14 +0000
Message-ID: <CAChbWaMjgVQcZivfUNu_gRyOHeOnhjWC=N3Uysa=dCMQkB5-Qg@mail.gmail.com>
To: Sushanth Ramakrishna <sushanth@seniorly.com>, public-schemaorg@w3.org
Then I just had a brain collapse...

What about some communities who might offer "medical care" but only for
SOME of their services and not others ?  Does that really happen in the USA
or UK or elsewhere ?

If so, how is that best represented ?  I imagine for each Service offered,
it could be an MTE as something like a MedicalService also ?  Dunno, but
that makes my head spin, thinking that an MTE might be needed on each
plausible Service that falls under some regulation and needs a Doctor or
Nurse to provide ?

I'll let you think that over a bit...
-Thad


On Tue, Dec 20, 2016 at 8:24 PM Thad Guidry <thadguidry@gmail.com> wrote:

> Its seems like the terms "non medical care" and "medical care" are a
> differentiator distinguishing some communities from others or of the care
> services they provide.
>
> I am concerned that the PR might not be flexible enough to state which
> communities offer "non medical care" versus "medical care" ?
> Isn't that an important consideration ?  Should that instead be a property
> as a boolean indicator perhaps ?  Those communities that offer "medical
> care" are they always known as nursing homes or can they be called
> something else at times ?
>
> (I noticed your subtle changes in the descriptions on the PR)
>
> Not my domain, but just thinking out loud.
> I found this website that seemed to sum up much of the amenities and
> services typically offered:
> http://www.alfa.org/alfa/Lifestyles_and_Amenities.asp
>
> -Thad
>
> On Tue, Dec 20, 2016 at 7:16 PM Sushanth Ramakrishna <
> sushanth@seniorly.com> wrote:
>
>> Hi Community,
>>
>> I need your input on my proposed extension. I have added vocabulary
>> around Senior Care Communities. My goal is to add structure around existing
>> senior care services to make it easier to discover and understand the
>> difference between applicable options.
>> (Disclosure : I am a developer at a Senior Care Marketplace company)
>>
>> I followed the example from Richard Wallis' work to extend the schema.
>>
>> *Quick summary of changes: *
>> Added types to represent Senior Housing Communities and certain
>> properties to enable easier understanding of care offered in these
>> communities.
>>
>> *PR on GitHub:* https://github.com/schemaorg/schemaorg/pull/1462
>>
>> *You can view the full changes here: *
>> https://sly-hosted-ext.appspot.com/SeniorHousingCommunity
>> https://sly-hosted-ext.appspot.com/SeniorCareService
>> https://sly-hosted-ext.appspot.com/AssistedLivingCare
>> https://sly-hosted-ext.appspot.com/MemoryCare
>> https://sly-hosted-ext.appspot.com/HospiceCare
>> https://sly-hosted-ext.appspot.com/AssistedLivingCommunity
>> https://sly-hosted-ext.appspot.com/MemoryCareCommunity
>>
>>
>> *References for terms: *
>> https://en.wikipedia.org/wiki/Assisted_living
>> http://www.nhpco.org/about/hospice-care
>> http://www.aplaceformom.com/blog/2013-3-4-assisted-living-vs-memory-care/
>>
>>
>>
>> Side Note: Google's knowledge graph seems to be aware of 'Assisted Living
>> Facility'  entity even though I did not find any references in the base or
>> searchable extensions on schema.org. If anyone on this forum is aware of
>> any existing pull requests or discussions, do point me in that direction.
>>
>> Do let me know If I am not doing things right or am missing key elements.
>> I appreciate any and all guidance to making the web a little more
>> understandable!
>>
>> Best,
>>
>> *Sushanth Ramakrishna*
>> Seniorly, Inc.
>> p:(415) 570 4370 <(408)+828-1734> | e:sushanth@seniorly.com | w:
>> seniorly.com <https://www.seniorly.com/>
>> <http://facebook.com/seniorly>  <http://twitter.com/seniorly>
>> <https://www.linkedin.com/company/seniorly>
>>
>>
Received on Wednesday, 21 December 2016 02:31:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:12:31 UTC