I am glad that we're clarifying this. I often get asked how RecordShape can help to figure out whether a property is required or not.
My two cents: Why not explicitly state which values mean that the property is REQUIRED, and which values indicate that the property is OPTIONAL. SUGGESTED DESCRIPTION: MUST be either http://open-services.net/ns/core#Exactly-one (property is REQUIRED), http://open-services.net/ns/core#One-or-many (property is REQUIRED), http://open-services.net/ns/core#Zero-or-one (property is OPTIONAL), or http://open-services.net/ns/core#Zero-or-many (property is OPTIONAL). ___________________________________________________________________________ Samit Mehta IBM Rational Software - Business Development mailto:[email protected] "Oslc-Core" <[email protected]> wrote on 11/13/2012 07:56:39 AM: > From: John Arwe/Poughkeepsie/IBM@IBMUS > To: [email protected], > Cc: Nils Kronqvist <[email protected]> > Date: 11/13/2012 07:57 AM > Subject: Re: [oslc-core] Clarification of the requiredness of a > property in a ResourceShape > Sent by: "Oslc-Core" <[email protected]> > > strawman for change attached, so if the working group feels a change > is worthwhile then perhaps we can move it along on tomorrow's call > Best Regards, John > > Voice US 845-435-9470 BluePages > Tivoli OSLC Lead - Show me the Scenario > [attachment "20121113OccursRequiredClarification.pdf" deleted by > Samit Mehta/San Francisco/IBM] _______________________________________________ > Oslc-Core mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-core_open-services.net
