Re: New hosted extension for DIF Identity Hub

Daniel,

I would say review thoroughly our http://schema.org/docs/extension.html and
http://schema.org/docs/howwework.html

In particular most of the challenge for Extension authors is avoiding
overlap of names since Schema.org is a flat namespace.... that's in
howwework.html  which states in particular that...

Schema.org property names are considered "global" across the entire project
(including the core and all hosted vocabularies such as "auto
<http://auto.schema.org/>", "bib <http://bib.schema.org/>" etc.). For
example, there is only one property such as "startDate
<http://schema.org/startDate>", and both its human-readable and
machine-readable definitions need to be appropriate to all the situations
in which it might be used. In the case of "startDate" (defined currently as
"The start date and time of the item"), the text has to be appropriate to
all of the different combinations of types it can be used with.

This situation drives many of the evolutionary changes to schema.org. Often
properties are added for some specific use case, and their potential
relationship to other areas of schema.org only becomes clear later. This
gives rise to changes in textual definition and property-to-type
associations that gradually make schema.org more coherent, without
introducing radical changes in meaning. Consumers of schema.org data can
generally rely on schema.org term meanings not changing dramatically;
however term definitions often evolve gradually over time, to accomodate
new usage scenarios or to improve usability.

A common change is for a property to be marked as applicable to some
previously unrelated type, or to expect to take values of a new type. When
this happens the textual definitions are often adjusted slightly too. This
is either by listing the new types explicitly, or through the use of a more
general term like "item", "entity" or "thing". The issue summaries in the
project releases <http://schema.org/docs/releases.html> page are a good
guide to the kind of changes to expect in future.

You'll want to continue to work with the community (this email is a great
start!) to review your Extension proposal and you'll probably get a bit of
drifting conversations from the community sometimes here and there, but
work with us so that we understand your needs, and you understand how to
align well with others efforts and existing extensions and upcoming
proposals.  We all have to play nicely in this "shared" sandbox we call
Schema.org.  At the end of the day, its all about getting agreement, which
is 99% of the challenge typically :)

-Thad