Nils, the Core WG discussed this issue today and updated the spec. The draft is available using the link from your original email. The updated description of oslc:occurs is as follows:
MUST be either http://open-services.net/ns/core#Exactly-one (property is required), http://open-services.net/ns/core#Zero-or-one (property is optional), http://open-services.net/ns/core#Zero-or-many (property is optional), or http://open-services.net/ns/core#One-or-many (property is required) Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario "Oslc-Core" <[email protected]> wrote on 11/06/2012 12:51:47 PM: > From: Nils Kronqvist <[email protected]> > To: [email protected] > Date: 11/06/2012 04:27 PM > Subject: [oslc-core] Clarification of the requiredness of a property > in a ResourceShape > Sent by: "Oslc-Core" <[email protected]> > > Hi, > > Minor suggestion on clarification of the ResourceShape spec .. > > Looking at http://open-services.net/bin/view/Main/ > OSLCCoreSpecAppendixA?sortcol=table;up=#oslc_ResourceShape_Resource > .. one purpose of Resource Shapes is to specify if a property is > allowed or required. How is the requiredness of a property > indicated? Is it the oslc:occurs property that is set to "zero to > one/many" signifies allowed and if "exactly one/one to many" > signifies required -- right? If so, would IMO be helpful to > explicitly point this out in the spec. > > Rgs, > > /N > > > [image removed] > > > Nils Kronqvist > Senior Software Engineer > Arne Beurlings Torg 9A, 4tr > 164 40 Kista > [email protected] > mobil: +46 76 1279272 > www.find-out.se > > > _______________________________________________ > Oslc-Core mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-core_open-services.net
