I agree that an oslc:instanceShape property makes sense in common properties.
I just added an issue to track this: 1 %RED%OPEN%ENDCOLOR% Add an =oslc:instanceShape= property to allow resources to specify their shape. See discussion here: http://open-services.net/pipermail/oslc-core_open-services.net/2010-April/000143.html (DaveJohnson 04/28/2010). * *Response* Yes, get this into spec (DaveJohnson 04/27/2010) Thanks, - Dave On Tue, Apr 27, 2010 at 8:09 AM, Steve K Speicher <[email protected]> wrote: > Another thing to consider, or be aware of, (at least for XML-based resource > formats), is this recent work by W3C XML Core WG titled "Associating > Schemas with XML documents 1.0" http://www.w3.org/TR/xml-model/ > > We'd need to obviously still come up with something for non-XML based > formats. > > So I'd still recommend a unique property for this. > > Thanks, > Steve Speicher | IBM Rational Software | (919) 254-0645 > > > Arthur Ryman <[email protected]> wrote on 04/26/2010 11:56:50 AM: > >> From: Arthur Ryman <[email protected]> >> To: Steve K Speicher/Raleigh/IBM@IBMUS >> Cc: [email protected], [email protected] >> Date: 04/26/2010 11:56 AM >> Subject: Re: [oslc-core] How do I get the shape from a resource? >> >> Steve, >> >> The rdf:type should be the OSLC type defined by the appropriate domain >> spec, e.g. CM. It belongs to the OSLC domain, http://open-services.net, so >> GETing it would NOT reflect any new properties added by a service >> provider. >> >> I agree that it would be handy to be able to easily find the shape of a >> resource. There are really two major use cases: >> >> 1. Schema-based information, e.g. to design a report. You need to find the >> shape from the service provider. This is what oslc:shape is for. >> >> 2. Instance-based information, e.g. you are given the URL of an instance >> resource and you want to find its shape, e.g. to modify the instance via >> PUT. There is no property defined yet. Using oslc:shape might be >> confusing. In XML Schema, they introduced a special namespace for instance >> level information such as type, xsi: >> http://www.w3.org/2001/XMLSchema-instance. >> >> To avoid confusion I suggest we use a different property, e.g. >> oslc:instanceShape >> >> 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: >> Steve K Speicher <[email protected]> >> To: >> [email protected] >> Date: >> 04/24/2010 03:06 PM >> Subject: >> [oslc-core] How do I get the shape from a resource? >> Sent by: >> [email protected] >> >> >> >> I had assumed that every OSLC defined resource would have an rdf:type >> property that references either the spec defined Type URI OR is it a >> gettable URI that references the service provider's hosted version of the >> resource shape. >> >> Here's my example, I have a OSLC-CM Change Request resource that looks >> like: >> >> <oslc_cm:ChangeRequest rdf:about="http://example.com/bugs/2314";> >> <rdf:type rdf:reference=" >> http://open-services.net/xmlns/cm/2.0#ChangeRequest";> >> </oslc_cm:ChangeRequest> >> >> Is it required for rdf:type to point to the OSLC defined Type URI? How >> do I get to the resource shape of this resource? >> >> I would instead think that we'd want an OSLC Common Property called >> "oslc:shape" which points to a gettable OSLC shape resource. Any >> objections to adding this? Any need use dc:type here instead (or clarify >> how it could be used) ? >> >> Thanks, >> Steve Speicher | IBM Rational Software | (919) 254-0645 >> _______________________________________________ >> Oslc-Core mailing list >> [email protected] >> http://open-services.net/mailman/listinfo/oslc-core_open-services.net >> >> >> > > _______________________________________________ > Oslc-Core mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-core_open-services.net > >
