[oslc-core] Changing dcterms:publisher in SPC & SP resources to be Resource and Either

David Johnson snoopdave at gmail.com
Fri Sep 3 14:57:15 EDT 2010


I think that value-type Either and representation Either are good defaults when we define resource properties.

In general, I think we should encourage workgroups to favor plain old links, avoid local resources, avoid in-lined values and being careful about placing restrictions on things.

- Dave


On Sep 3, 2010, at 10:46 AM, Scott Bosworth wrote:

> +1. I wonder, is "either" the value that we should view as the default value-type when considering resource properties?
> 
> 
> 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-bounces at open-services.net wrote on 09/03/2010 10:14:19 AM:
> 
> > From: Steve K Speicher/Raleigh/IBM at IBMUS
> > Subject: [oslc-core] Changing dcterms:publisher in SPC & SP 
> > resources to be Resource and Either
> > 
> > Both the oslc:ServiceProvider and oslc:ServiceProviderCatalog resource 
> > definitions [1] have a property of oslc:publisher.  I have received some 
> > feedback from implementers that it would be better if the definition were 
> > made more flexible to instead be:
> > 
> > oslc:publisher - Valule-type: Resource - Representation: Either
> > (to allow for the Publisher information to live as a URI referencable 
> > resource)
> > 
> > Any issues with making this change?
> > 
> > [1] 
> > http://open-services.net/bin/view/Main/OslcCoreSpecification?
> > sortcol=table;table=up;up=#Resource_Service_Provider_Catalo
> > 
> > P.S.  I wonder if we should relax our definition of these rules a bit. 
> > They were originally intended for defining a serialization model but 
> > clients should be prepared for most alternative formats (referenced vs. 
> > inlined).  For example, a client should not depend on a service to define 
> > resources that match the spec representation statements exactly (even if 
> > it says it is a Local Resource, expect anything).
> > 
> > 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





More information about the Oslc-Core mailing list