Re: Schema.org External Enumerations mechanism

Schema.org already offers an extension mechanism:
http://schema.org/docs/extension.html - it might help some people to
understand the difference between the external enumeration mechanism and
the extension mechanism, is there an overlap between the two, does it
deprecate the old mechanism, and if not, how do they complement each
other...



I don't understand the snippet below "Here is an example using a direct
link to a controlled value page:". What am I missing? I would have expected
to see a link element using the 'about' property. Did you intend to link to
http://id.loc.gov/authorities/sh85003441#concept maybe?



Slightly confused regarding the scope of wikipedia. The definition of the
wikipedia scope is: "Namespaces follow Wikipedia naming, so the English
namespace is 'en', etc.These identifiers should also map cleanly to
DBpedia's. "
<aside>'Namespaces' should probably be named scope or scope in the context
of the named scope column</aside>

However I find these examples in the draft:
http://ext.schema.org/wikipedia/countries/Canada
http://ext.schema.org/wikipedia/en/United_States
http://ext.schema.org/wikipedia/en/{term} to
http://en.wikipedia.org/wiki/{term} (test case: term=United_States)
http://ext.schema.org/wikipedia/resource/{term} to
http://en.wikipedia.org/wiki/{term} (test case: term=Lonclass)

>From these example, scope can be 'en', 'countries' or 'resource'. Is that
intended? Is 'en' used as a kind of catch all scope? What about 'resource'?


Looking good otherwise!

Steph.

On Thu, Apr 19, 2012 at 2:30 PM, Dan Brickley <danbri@danbri.org> wrote:

> There is a near-final draft in the Wiki at
> http://www.w3.org/wiki/WebSchemas/ExternalEnumerations describing a
> mechanism for including externally enumerated datasets within
> schema.org.
>
> The approach we adopt tries to find a middle-ground between some
> design constraints. We want a simple, regular notation for schema.org
> publishers, while also drawing on various rich and detailed
> collections of identifiers found 'out there' in the decentralized Web.
> At schema.org we will maintain a list of supported datasets /
> vocabularies, and we'll configure URIs at ext.schema.org to correspond
> to entries in a variety of systems (e.g. Wikipedia/Wikidata, UDC,
> LCSH, UN FAO country codes, ...). Although individual search engines
> may decide to consume other patterns, at this stage the only
> collective commitment expected is that URLs matching
> http://ext.schema.org/* will be recognised as belonging to "external
> enumerations" that extend and enrich schema.org.
>
> The expectation is that this will improve schema.org's expressive
> coverage without bloating the core schema. If you look at our current
> schema, you'll see for example 27 or so subclasses of
> http://schema.org/LocalBusiness ... quite a list, and yet not enough
> to exhaustively cover things. Or http://schema.org/PlaceOfWorship
> which has six subtypes listing specific kinds of places of worship.
> The schema.org partners (or the W3C Web Schemas group) aren't the
> right people to come up with detailed lists of such things - it would
> be a neverending task. Rather, we need a mechanism that integrates
> such detail into the existing descriptive machinery provided by the
> core schema.org schema. To address this, schema.org external
> enumerations mechanism should be able to supply both property values
> and sub-types; we'll elaborate on Units and Measures in a later
> revision.
>
> Questions and comments to this list please,
>
> cheers,
>
> Dan
>
>