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

[Dave]

Each property specified in a Resource Shape needs to have an oslc:name
so that we can determine how to represent its values in a XML, JSON
and other formats.

The rule for forming an RDF property URL is simple concatenation, so
the namespace URL can be determined by removing the name from the end
of the oslc:propertyDefinition and that seems good enough to me -- and
that's why we removed the namespace URI from oslc:Property.

- Dave


On Thu, Aug 19, 2010 at 4:23 PM, Steve K Speicher <sspeiche at us.ibm.com> wrote:
> 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
>
> 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
>