[oslc-core] Defining domain namespaces

[Steve K Speicher]

Even though there are subdomains, I wonder if "Estimation and Measurement" 
will ever fall under any other parent domain.

A nit but agree, domains could manage their own subdomains.

Thanks,
Steve Speicher | IBM Rational Software | (919) 254-0645


Arthur Ryman <ryman at ca.ibm.com> wrote on 06/17/2010 03:44:09 PM:

> From: Arthur Ryman <ryman at ca.ibm.com>
> To: Steve K Speicher/Raleigh/IBM at IBMUS
> Cc: oslc-core at open-services.net, oslc-core-bounces at open-services.net
> Date: 06/17/2010 03:44 PM
> Subject: Re: [oslc-core] Defining domain namespaces
> 
> Steve,
> 
> +1.
> 
> We need some wiki page to register the {domain} part. 
> 
> We should allow domains to further manage the namespace for subdomains, 
> e.g. in Software Project Management domain I'd like to use spm as my 
> domain name, but I'd like to manage the namespace among difference 
> specifications, e.g. use ems for Estimation and Measurement Service. 
> Therefore the namespace for that spec would be:
> 
> http://open-services.net/ns/spm/ems#
> 
> Regards, 
> 
___________________________________________________________________________ 

> 
> Arthur Ryman, PhD, DE
> 
> 
> Chief Architect, Project and Portfolio Management
> 
> IBM Software, Rational
> 
> Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063
> Twitter | Facebook | YouTube
> 
> 
> 
> 
> 
> 
> 
> From:
> Steve K Speicher <sspeiche at us.ibm.com>
> To:
> oslc-core at open-services.net
> Date:
> 06/17/2010 02:08 PM
> Subject:
> [oslc-core] Defining domain namespaces
> Sent by:
> oslc-core-bounces at open-services.net
> 
> 
> 
> Dave and I were just making sure we were in alignment with namespace URI 

> definitions across the domains and going forward.
> 
> The guidance includes defining a namespace URI structure that matches:
>         http://open-services.net/ns/{domain}# 
> 
> So for CM 2.0, even though we had a 1.0 spec with 1.0 in the namespace 
> URI, we'll have:
>         http://open-services.net/ns/cm# 
> 
> The value of doing this, and nailing it down now, is:
> - Uniform across all domain specs, including a "final" change to the 
Core 
> NS to be http://open-services.net/ns/core# 
> - Additional properties can be added in existing namespaces for existing 

> resources.
>    Example, adding a property to oslc_cm:ChangeRequest, we'll just add 
it 
> and shapes can be used to discover the addition of them
> 
> There is some precedence for this in Dublin Core, as DC went from: 
> http://purl.org/dc/elements/1.1/ to http://purl.org/dc/terms/
> 
> Please raise any concerns or objections.
> 
> Thanks,
> Steve Speicher | IBM Rational Software | (919) 254-0645
> 
> 
> _______________________________________________
> Oslc-Core mailing list
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net
> 
> 
>