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

[Sofia Yeung]

That was my understanding too. That said, it should be translable - I18N, right? 



I'm sure what exactly we should get from oslc:propertyDefinition URI? Is there any sample for this? 



Thanks, 

-- Sofia 
----- Original Message ----- 
From: bosworth at us.ibm.com 
To: oslc-core at open-services.net 
Sent: Monday, August 23, 2010 7:57:38 AM GMT -08:00 US/Canada Pacific 
Subject: Re: [oslc-core] ResourceShape usage of oslc:name in conjunction with oslc:propertyDefinition 





> 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) 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20100823/6f679746/attachment-0003.html>