On Thu, Sep 25, 2014 at 9:24 AM, Vicki Tardif Holland <vtardif@google.com> wrote: > > On Thu, Sep 25, 2014 at 9:16 AM, Dan Brickley <danbri@google.com> wrote: > >> > If you really want to go down this route, though, I would suggest >> roleName >> > directly on Role that could serve for any future subtypes as well. >> > Otherwise, properties like characterName and namedPosition are just >> going to >> > propagate as more Role subtypes emerge for different contexts. >> >> roleName on Role (expecting Text or URL) works for me, > > > > Promoting "namedPosition" to Role and renaming the property "roleName" or > the like soungs good to me. > > Thanks for the positive response, Vicki! I've opened https://github.com/rvguha/schemaorg/pull/146 in the hopes of making this (or the like) happen.
Received on Thursday, 9 October 2014 19:46:59 UTC