Re: how to go about creating a new vocab?

On 05/02/2013 12:48 PM, Marian, Radu 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 ?
>

One option is to create a W3C Community Group.   That gives you a 
mailing list (with public archives) and a wiki for the development 
stage.   It also give you the namespace 
http://www.w3.org/ns/your-group-name.   (With a bit of discussion we can 
probably make that namespace differ from the group name, or have several 
namespaces.)    When the group is ready to post or revise its namespace 
document, email me and/or the webmaster at webreq@w3.org.   (I'm working 
on a webform to do that publishing automatically, but for now we'll do 
it by hand.  We're in the process of starting to be more public about 
this service.)

For more information on creating Community Groups, see: 
http://www.w3.org/community/

I should point out that if you do it this way, W3C owns the vocabulary.  
As long as the Community Group is working well by consensus, I doubt 
anyone will notice or care.   But if at some point there is a  dispute, 
it'll be up to W3C process (involving the Director and possibly the 
Members) to settle it.   This will be comforting to some people, but if 
it's not how you want things to work with this vocabulary, then this 
isn't a good option.

I hope this helps.

         -- Sandro  (and thanks to danbri for tagging me on this discussion)

> On May 2, 2013 11:15 AM, "Marian, Radu" <radu.marian@baml.com 
> <mailto: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 <tel:%28704%29%20628-6874>
> an Enterprise without Ontology is like a country without a map.
>
>
> -----Original Message-----
> From: Alexey Zakhlestin [mailto:indeyets@gmail.com 
> <mailto:indeyets@gmail.com>]
> Sent: Thursday, May 02, 2013 11:40 AM
> To: Marian, Radu
> Cc: public-vocabs@w3.org <mailto: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 
> <mailto: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 <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.