revising Extension Mechanism

Hello,

Currently documentation recommends using '/' for 'extending' schema.org
http://schema.org/docs/extension.html

for example:

Person/Engineer/ElectricalEngineer
musicGroupMember/leadVocalist

To my understanding this approach violates URI Opacity[1] and doesn't
allow dereferencing terms 'extended' in such way.

In one of previous emails I suggested one of possible alternatives, to
instead of schema:Action/HugAction use multiple types schema:Action
ex:HugAction

JSON-LD:
{
  "@context": ["http://schema.org", { "ex": "http://example.net/#" }]
  "@type": ["Action", "ex:HugAction"],
  ...
}

Currently http://bibliograph.net looks like nice example of extension
[2]. Maybe some of numerous 'medical' schemas could also become
eventually some kind of medigraph?

Also GoodRelations stays in sync and also could give good example of
providing more advanced features on top of those directly incorporated
in schema.org

Besides that some of the people partcipating in Social WG might consider
leveraging WebSchemas work. To my understanding it would require solid
extension mechanism to accommodate for example needs of Activity Streams
2.0 Vocabulary[3] Possibly a topic for face 2 face meeting during TPAC[4] ?

Last but not least http://vocab.gtfs.org looks like another vocab which
could potentially extend schema.org. GTFS started as 'Google Transit
Feed Specification' and I hope new RDF vocab could also work with Rich
Snippets etc.

I realize that everyone stays super busy and we may not find enough
cycles to give this topic enough attention. Still maybe worth trying to
start with gathering feedback and ideas?

Cheers!

[1] http://www.w3.org/TR/webarch/#uri-opacity
[2] http://www.slideshare.net/rjw/extending-schemaorg
[3]
http://jasnell.github.io/w3c-socialwg-activitystreams/activitystreams2-vocabulary.html
[4] https://www.w3.org/wiki/TPAC2014/SessionIdeas#Schema.org_and_Social_WG

Received on Sunday, 19 October 2014 21:52:22 UTC