Re: how to go about creating a new vocab?

Radu:

The OMR is a service designed to give the vocabulary owner (an important
concept for us) the tools to manage and publish vocabularies.  We have user
management controls in place--the admin that is (or represents) the owner
makes the decisions about who among designated maintainers has specific
permissions.

Most of our larger vocabulary owners prefer to use their own domain, and we
can assist in providing appropriate content negotiation for external
domains. Whether our domain or external domains are used, we do not claim
ownership over the content provided by others through the OMR. Owners are
free to export or move their vocabularies at any time. Our upgraded system
will include improvements in several areas, including user management,
private as well as public vocabularies, the ability to manage vocabularies
locally and upload them to the OMR for distribution/availability for
others, and semantic mapping.

Diane


On Thu, May 2, 2013 at 3:22 PM, Marian, Radu <radu.marian@baml.com> wrote:

>  Diane,****
>
> ** **
>
> Thanks for pointing out to metadataregistry.org. I believe it addresses
> the discoverability aspect.  What about legal perspective?  Does it carry
> the legal weight to its identifiers in contracts between enterprise and
> cloud server providers – specifically in regards to user permission
> provisioning?****
>
> ** **
>
> Ralph – thanks for pointing this out.  I wonder if Oasis has some kind of
> registry of its vocabularies?****
>
> ** **
>
> 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.***
>
> ** **
>
> *From:* LeVan,Ralph [mailto:levan@oclc.org]
> *Sent:* Thursday, May 02, 2013 3:02 PM
> *To:* Diane Hillmann; Marian, Radu
>
> *Cc:* Thad Guidry; public-vocabs@w3.org; Alexey Zakhlestin
> *Subject:* RE: how to go about creating a new vocab?****
>
>  ** **
>
> I’ve done standards work in OASIS and they’re pretty possessive about the
> work products from their committees.  They’re going to want to be the ones
> to control this schema.****
>
> ** **
>
> Ralph****
>
> ** **
>
> *From:* Diane Hillmann [mailto:metadata.maven@gmail.com]
> *Sent:* Thursday, May 02, 2013 1:50 PM
> *To:* Marian, Radu
> *Cc:* Thad Guidry; public-vocabs@w3.org; Alexey Zakhlestin
> *Subject:* Re: how to go about creating a new vocab?****
>
> ** **
>
> 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.****
>
> ** **
>  ------------------------------
> 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.
>