[oslc-core] Issue: do we really need 4 resource value-types?

Arthur Ryman ryman at ca.ibm.com
Fri May 28 16:02:58 EDT 2010


Nick/Dave,

The EMS 1.0 spec uses them.

BTW, the inline and local terms are just ways of talking about blank 
nodes. RDF leads you to the introduction of blank nodes. If we change 
anything, maybe we should simply stop trying to shield people from RDF and 
get them to learn the real terms instead of inventing new ones to reduce 
RDF-shock. Perhaps we are replacing it with OSLC-shock?

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:
Nick Crossley <ncrossley at us.ibm.com>
To:
oslc-core <oslc-core at open-services.net>
Date:
05/28/2010 01:02 PM
Subject:
Re: [oslc-core] Issue: do we really need 4 resource value-types?
Sent by:
oslc-core-bounces at open-services.net



We use Resource, Inline Resource, and Local Inline Resource in SCM (I 
think!) 

Nick. 



From:        Dave <snoopdave at gmail.com> 
To:        oslc-core <oslc-core at open-services.net> 
Date:        05/28/2010 08:08 AM 
Subject:        [oslc-core] Issue: do we really need 4 resource 
value-types? 
Sent by:        oslc-core-bounces at open-services.net 



I like the four value-types that Arthur proposed and they've been in
the spec draft for some time now, but I wonder: do we need them all?

  See also -> 
http://open-services.net/pipermail/oslc-core_open-services.net/2010-April/000111.html


Here's an issue I just raised on the issues page:

  1 OPEN We have defined value-types Resource, Inline Resource, Local
Resource and Local Inline Resource. Do we really truly need all of
these types? We want representation to be simple and use flat
name/value property model, so should we give them all these value
types? Can we live without Local Resource? What about Local Inline
Resource? Do we have use cases to support these things?

     * Response: pending...

Any opinions on this?

Thanks,
Dave

_______________________________________________
Oslc-Core mailing list
Oslc-Core at open-services.net
http://open-services.net/mailman/listinfo/oslc-core_open-services.net
_______________________________________________
Oslc-Core mailing list
Oslc-Core at open-services.net
http://open-services.net/mailman/listinfo/oslc-core_open-services.net






More information about the Oslc-Core mailing list