Re: Request for Comment: schema.org/InsurancePlan

Very First,

Get existing examples of data out there now that might include HTML, or RDF
or Microdata or whatever schema format... you'll need this backbone of
first hand experience and information to drive recommendations and align
your schema experiments towards what, how, where, when the data and
properties and classes are used now in the existing web...to help begin to
make them searchable as real Linked Data with your schema.org proposals or
extensions.

First,

Define what an InsurancePlan is.  That definition will be used to steer
people with a good description of the Type (and latter perhaps...additional
Classes under that new Type called InsurancePlan ... like
schema.org/InsurancePlan/ForUninsuredSingleMothers or
schema.org/InsurancePlan/NoPremiumsEver!!!  :) ,... which might have their
own unique properties under each ... whatever the needs of the community
and domain stakeholders will feel will be necessary...which means You, and
others in the Insurance industry or those interested.)

Second,

Gather up all the potential properties that you think would fit under an
InsurancePlan and list them.  Then send reply with that list to our mailing
list, so that others can think about it, look at them, make suggestions,
refinements, etc.  (I.E. Get the conversation started and show motivation
towards the Insurance industry, stakeholders, and needs of web developers)

Third,

Begin formalizing your plans and ideas into the wiki starting here (where
you can see up and coming proposals just like your need):
http://www.w3.org/wiki/WebSchemas/SchemaDotOrgProposals

Fourth,

Do not know what Fourth should be... perhaps Dan can speak about that ?

References,

http://schema.org/docs/documents.html

Hope that helps !




On Tue, Oct 22, 2013 at 7:00 PM, Wes Turner <wes.turner@gmail.com> wrote:

> Hypothetically, how would one go about creating a
> schema.org/InsurancePlan ?
>
>


-- 
-Thad
Thad on Freebase.com <http://www.freebase.com/view/en/thad_guidry>
Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/>