> Are we uncomfortable with this idea of standardizing APIs? I do imagine some APIs warrant standardization and OASIS involvement and others do not. That's why In my mind, the question of standardizing APIs doesn't help me wrap my head around the concept as much as questions about standardizing a specific API. I started to think about my previous questions when I saw such a deep divide in the board discussion - some board members thought standardization would be a great benefit, some board members didn't seem at all convinced. BUT, I think the difference in opinion could easily have been driven by whatever "example API" each board member was thinking about at the time of the general discussion. If that bifurcation of opinion about standardization is based on the specific API, then let's focus our energy on the ones that are more likely a winner. (Again noting I can't tell one from the other) Scott... On Wed, Nov 6, 2013 at 5:25 PM, Laurent M Liscia <
laurent.liscia@oasis-open.org> wrote: > Almost sounds like you want to talk them out of it ;-) . > Are we uncomfortable with this idea of standardizing APIs? > > -- > Laurent Liscia, CEO > OASIS: Advancing open standards for the information society > (510) 669-1261 > > > Follow OASIS on: > LinkedIn:
http://linkd.in/OASISopen > Twitter:
http://twitter.com/OASISopen > Facebook:
http://facebook.com/oasis.open > > Take a tour of OASIS at: >
http://www.oasis-open.org/home/tour.php > > > > > On 11/6/2013 2:20 PM, Scott McGrath wrote: >> >> Do they need standardization? By that I mean: >> >> Do they need a formally documented, branded standard document that is >> openly published and assured to be available forever? Who is >> clamoring for that? What buying decision of our members' customers is >> based on that standard? >> >> If they do need standardization, do they need OASIS? By that I mean: >> >> Do they need our community,our ability to create a community, our >> rules, our tools, or our brand on the document? >> >> Lastly, if we think the needs exist - does their community and >> marketplace? >> >> As I think about APIs in general, I do not think the need exists in >> some (many??) cases. But I also imagine there are APIs where the need >> does significantly exist. I just don't think *I* can tell one from >> the other. >> >> Scott... >> >> On Wed, Nov 6, 2013 at 3:59 PM, Jamie Clark <
jamie.clark@oasis-open.org> >> wrote: >>> >>> Let's start with "obviously APIs can be created under the JCP, and thus >>> almost certainly at OASIS." Jamie >>> >>> >>> On Tue, Nov 5, 2013 at 3:24 AM, Dee Schur <
dee.schur@oasis-open.org> >>> wrote: >>>> >>>> Any thought on the Java Identity API? >>>> >>>> dee >>>> >>>> >>>> >>>> From: David Brossard [ mailto:
david.brossard@axiomatics.com ] >>>> Sent: Monday, November 04, 2013 5:51 PM >>>> To: xacml; Dee Schur >>>> Subject: Fwd: [OpenAz] links to JSR-351 : The Java Identity Api >>>> >>>> >>>> >>>> This came in on the Open AZ list. It could be relevant to the work we do >>>> within the XACML TC. Do you think it could apply to other OASIS TCs e.g. >>>> SAML? >>>> >>>> >>>> >>>> Thoughts? >>>> >>>> ---------- Forwarded message ---------- >>>> From: Prateek Mishra <
prateek.mishra@oracle.com> >>>> Date: Mon, Nov 4, 2013 at 11:09 PM >>>> Subject: [OpenAz] links to JSR-351 : The Java Identity Api >>>> To:
openaz@lists.openliberty.org >>>> >>>> >>>> 1. Proposed Api with Overview >>>>
http://jcp.org/aboutJava/communityprocess/edr/jsr351/index.html >>>> >>>> 2. Website >>>>
https://java.net/projects/identity-api-spec/pages/Home >>>> _______________________________________________ >>>> OpenAz mailing list >>>>
OpenAz@lists.openliberty.org >>>>
http://lists.openliberty.org/mailman/listinfo/openaz >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> David Brossard, M.Eng, SCEA, CSTP >>>> Product Manager >>>> +46(0)760 25 85 75 >>>> Axiomatics AB >>>> Skeppsbron 40 >>>> S-111 30 Stockholm, Sweden >>>> LinkedIn:
http://www.linkedin.com/companies/536082 >>>> Web:
http://www.axiomatics.com >>>> Twitter:
http://twitter.com/axiomatics >>>> >>>> Google Plus:
https://plus.google.com/u/1/109113357550030353531/ >>> >>> >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: >
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php -- Scott McGrath COO
scott.mcgrath@oasis-open.org Tel +1 781-425-5073 x202 Fax +1 781-425-5072 Follow OASIS on: LinkedIn:
http://linkd.in/OASISopen Twitter:
http://twitter.com/OASISopen Facebook:
http://facebook.com/oasis.open