- From: Diane Hillmann <metadata.maven@gmail.com>
- Date: Thu, 2 May 2013 13:49:40 -0400
- To: "Marian, Radu" <radu.marian@baml.com>
- Cc: Thad Guidry <thadguidry@gmail.com>, "public-vocabs@w3.org" <public-vocabs@w3.org>, Alexey Zakhlestin <indeyets@gmail.com>
- Message-ID: <CAEXEg8qG4c4Ks4O6Q7zGi_TOQ5A0a9D7KA3Xq5-4eOTAgZMwgg@mail.gmail.com>
Have you looked at the Open Metadata Registry (metadataregistry.org)? We've been around for a while and currently provide vocabulary development services for free. We're actively working on upgrades and additions to the services. Diane Hillmann Metadata Management Associates On Thu, May 2, 2013 at 12:48 PM, Marian, Radu <radu.marian@baml.com> wrote: > That is correct Thad – thanks for clarification.**** > > ** ** > > *Radu Marian,* MSCS, SCEA, CISSP**** > > Bank of America - Charlotte, NC **** > > VP, Architect 2, Enterprise Security > Architecture ** > > Business phone number: (704) 628-6874**** > > *an Enterprise without Ontology is like a country without a map.*** > > ** ** > > *From:* Thad Guidry [mailto:thadguidry@gmail.com] > *Sent:* Thursday, May 02, 2013 12:20 PM > *To:* Marian, Radu > *Cc:* public-vocabs@w3.org; Alexey Zakhlestin > *Subject:* RE: how to go about creating a new vocab?**** > > ** ** > > I think you are really asking where you can store your draft vocabulary , > work on it, and then later publish it ?**** > > On May 2, 2013 11:15 AM, "Marian, Radu" <radu.marian@baml.com> wrote:**** > > Alex, > > Thank you - I did see them both. They may satisfy basic Web and Social > access control needs. > > However our goal is to standardize on an IAM vocabulary in > Cloud/Enterprise. It should cover all IAM phases - Access Design, Request, > Approval, Provisioning, Runtime, Review, Analytics, and Reconciliation. > > Here is the latest model snapshot > https://www.oasis-open.org/apps/org/workgroup/cloudauthz/download.php/49053/entitlement.ontology.png > > P.S. I am working on a write-up to describe this model. > > Regards, > Radu Marian, MSCS, SCEA, CISSP > Bank of America - Charlotte, NC > VP, Architect 2, Enterprise Security > Architecture > Business phone number: (704) 628-6874 > an Enterprise without Ontology is like a country without a map. > > > -----Original Message----- > From: Alexey Zakhlestin [mailto:indeyets@gmail.com] > Sent: Thursday, May 02, 2013 11:40 AM > To: Marian, Radu > Cc: public-vocabs@w3.org > Subject: Re: how to go about creating a new vocab? > > > On 02.05.2013, at 19:26, "Marian, Radu" <radu.marian@baml.com> wrote: > > > Dear Public Vocabs Community, > > > > At OASIS we have started a CloudAuthZ TC which is creating a new access > control model. > > > > We would like to create an access control vocabulary similar to > http://schema.org. We do have a draft model ontology for access control > - however we need to move from ontology design into vocabulary registration. > > > > So the question - is where do we start? What is the simplest way to > build such a vocabulary? > > > > P.S. The vocab that we have in mind is not necessarily for Web use but > rather for Enterprise and Cloud. > > Did you see these ones? > > http://www.w3.org/wiki/WebAccessControl > http://sioc-project.org/ontology#sec-modules-access > > What would be advantage of your vocabulary? > > > > -- > Alexey Zakhlestin > CTO at Grids.by/you > https://github.com/indeyets > > > > > > > ---------------------------------------------------------------------- > This message, and any attachments, is for the intended recipient(s) only, > may contain information that is privileged, confidential and/or proprietary > and subject to important terms and conditions available at > http://www.bankofamerica.com/emaildisclaimer. If you are not the > intended recipient, please delete this message.**** > ------------------------------ > This message, and any attachments, is for the intended recipient(s) only, > may contain information that is privileged, confidential and/or proprietary > and subject to important terms and conditions available at > http://www.bankofamerica.com/emaildisclaimer. If you are not the intended > recipient, please delete this message. >
Received on Thursday, 2 May 2013 17:50:12 UTC