[oslc-core] ResourceShape usage of oslc:name in conjunction with oslc:propertyDefinition

[Steve K Speicher]

Upon further review, here is what the properties are used for (in my own 
words):

oslc:name - localname part of QName, ie XML element name.  for example 
"implementedBy"
dc:title - a meaningful label suitable for presentation to an end user, 
for example "Implemented by"
oslc:propertyDefinition - full URI identifier for the property definition 
(oslc:propertyDefinition is a concatenation of namespace URI + oslc:name), 
for example "http://www.open-services.net/ns/cm#implementedBy"

Problem is that shape properties are defined in 2 different places with 
slightly different text, see [1] and [2].  I propose that [1] be a textual 
high-level definition of resources and point to [2] to be a more detailed 
definition, with property definitions, value types,  with allowed values, 
etc.

[1] 
http://open-services.net/bin/view/Main/OslcCoreSpecification#OSLC_Defined_Resources
[2] 
http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixA#oslc_ResourceShape_Resource

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


oslc-core-bounces at open-services.net wrote on 08/23/2010 10:57:03 AM:

> From: Scott Bosworth/Raleigh/IBM at IBMUS
> To: oslc-core at open-services.net
> Date: 08/23/2010 10:57 AM
> Subject: Re: [oslc-core] ResourceShape usage of oslc:name in 
> conjunction with oslc:propertyDefinition
> Sent by: oslc-core-bounces at open-services.net
> 
> 
> > Regarding oslc:name  What is this required or needed at all?  Can this 
be 
> > determined from the oslc:propertyDefinition URI ?  The oslc:name 
doesn't 
> > have any namespace URI.  The usage of it seems redundant and error 
prone. 
> > Though do we make any guarantees on how to split the 
> > oslc:propertyDefinition URI after hash # to determine the name or is 
there 
> > even a need?
> > 
> > See 
> > http://open-services.net/bin/view/Main/
> > OSLCCoreSpecAppendixA#oslc_ResourceShape_Resource
> 
> 
> I thought oslc:name was there for the purposes of having a human 
> readable label that could be presented to end users in something 
> like a query builder or other ui? This seems like a different 
> purpose than oslc:propertyDefinition? 
> 
> 
> 
> Scott Bosworth | IBM Rational CTO Team | bosworth at us.ibm.com | 919.
> 486.2197(w) | 919.244.3387(m) | 919.254.5271(f)
> _______________________________________________
> Oslc-Core mailing list
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net