- From: Eric Franzon <eric.franzon@gmail.com>
- Date: Wed, 23 Aug 2017 14:28:54 -0600
- To: Pete Rivett <pete.rivett@adaptive.com>
- Cc: "schema.org Mailing List" <public-schemaorg@w3.org>
- Message-ID: <CALWjsy-aB2BnxZFuTbAd+DfW2PxvLLqTmsnGo4GtU2r7j4e+XQ@mail.gmail.com>
Excellent points, Pete. The thought that got the ball rolling was, "how might I model the license issued by the state of Illinois to this specific plumbing business?" and I can see utility in defining both the specific license held by that business and in describing the broader nature of the license itself. That said, I suspect the schema.org scenario would allow for schema.org consumers to provide searchers with better results for a query such as: - "Licensed contractors near me" - "How can I see if this contractor's license is valid?" This use is better suited to licenses where there is a desire on the license holder's part to make the license transparent and public (as opposed to a Driver's License, Passport Number, subscription to a paywall, etc.). The broadened scope you pose is good food for thought, and it raises lots of questions about privacy, security, access control, and the like. In those more sensitive cases, though, I wonder if there isn't usefulness in describing types of licenses, as you posit above, so that users might get answers to queries such as: - What licenses apply to hair salons in Los Angeles? - When must I apply for a license to fish for salmon in the UK this year? - How many parking permits will be issued in 2018 at Chicago's McCormick Place and what is the process to get one? --Eric On Wed, Aug 23, 2017 at 2:03 PM, Pete Rivett <pete.rivett@adaptive.com> wrote: > Firstly are we talking about types of license (e.g. California Driving > License) or specific instances (e.g. Pete’s California Driving License with > number NNNN). I’m guessing Eric you have in mind the latter, but not sure > what Schema.org scenarios would need that. I suppose it could be useful > information about a business e.g. whether an Electrician is licensed. Not > sure about driving licenses though. > > > > Other things: > > - Who the license is issued to (Organization/Person) > - Geography/location (e.g. a driving license is for a particular > country, a fishing license for a particular area) > - Terms and conditions > > There may be value in distinguishing who is providing the license (DMV > generally) and who actually issued it (e.g. a specific DMV office or clerk) > > > > Would this also apply to: > > - Passports (could be viewed as a license to travel) > - software licenses? > - license to watch HBO or access NY Times paywall on n devices? > > > > Pete > > > > > > Pete Rivett (pete.rivett@adaptive.com) > > CTO, Adaptive Inc > > 65 Enterprise, Aliso Viejo, CA 92656 > > cell: +1 949 338 3794 <(949)%20338-3794> > > Follow me on Twitter @rivettp or http://twitter.com/rivettp > > > > > > > > > > > > > > *From:* Eric Franzon [mailto:eric.franzon@gmail.com] > *Sent:* Wednesday, August 23, 2017 12:47 PM > *To:* schema.org Mailing List <public-schemaorg@w3.org> > *Subject:* Proposal for defining licenses > > > > Hi All, > > > > I'm thinking that there is a need for license as a property beyond the > current domain and range defined in http://schema.org/license. > > > > Licenses can be held by a Person or Organization to perform a particular > action (hunting, fishing, demonstrating, busking, driving, operating a > particular piece of equipment, operating a business, providing a regulated > service, etc.). > > > > Would this be best as a new type (maybe child of CreativeWork?) leveraging > new and existing properties such as: > > - licenseNumber: (text) > - licenceType: (text) > - licenseIssuedBy: (Organization/Person) > - dateIssued: http://schema.org/dateIssued (Date - currently only > applies to tickets) > - expires: http://schema.org/expires (Date - currently on > CreativeWork) > > I'm just beginning to think on this, but have already run into several use > cases "in the wild" that could benefit from being able to explicitly state > a particular license. > > > > Does anyone else see this need? > > > > Thanks, > > --Eric > > > > -- > > *Eric Axel Franzon* > > > > LinkedIn: http://www.linkedin.com/in/ericfranzon > > Twitter: http://twitter.com/EricAxel > > > -- *Eric Axel Franzon* LinkedIn: http://www.linkedin.com/in/ericfranzon Twitter: http://twitter.com/EricAxel G+: http://http://gplus.to/ericfranzon
Received on Wednesday, 23 August 2017 20:29:18 UTC