Last week's meeting

Meeting logistics

See the OslcCoreMeetings for more information, more dial-in numbers and on-line meeting information.

• Conference Access
  • Toll free: 1-866-423-8350
  • Toll: 1-719-387-8273
• Participant passcode: 558663

Agenda

• AI Dave J: add rdfs:member to common properties
  • DONE - http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixA#RDFS_Properties

• AI Dave J: propose clarification for rdfs:member
  • NO ACTION - Read over Appendix B section "Specifying the shape of a query result" and with the addition of rdfs:member to common properties, I think we are covered.
    • http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixB#Specifying_the_shape_of_a_query

• Clarifications sought for Resource Shape oslc:readOnly
  • http://open-services.net/pipermail/oslc-core_open-services.net/2010-October/000600.html
  • RESPONSE:
    • Accept:
      • "true if the property is read-only. If not set, or false, the property is writable."
      • "Providers SHOULD declare a property read-only when changes to the value of that property will not be accepted on PUT. Consumers should note that the converse does not apply: providers MAY reject a change to the value of a writable property."
    • Defer:
      • Give oslc:readOnly is of type xsd:boolean, we adopt the lexical space defined by XSD (true, false, 0, 1).

• Issues with Resource Shape allowed values
  • http://open-services.net/pipermail/oslc-core_open-services.net/2010-October/000603.html
  • RESPONSE: clarify spec to say that allowed values is the union of those specified in-line and out-of-line

• Clarifications sought for oslc:range
  • http://open-services.net/pipermail/oslc-core_open-services.net/2010-October/000601.html
  • RESPONSE: Accept Ian's proposed clarification:
    • "For properties with a resource value-type, Providers MAY also specify the range of possible resource classes allowed, each specified by URI. The default range is http://open-services.net/ns/core#Any."

• Questions about Atom representations of query results
  • http://open-services.net/pipermail/oslc-core_open-services.net/2010-October/000602.html
  • RESPONSE: clarify guidance as follows "OSLC domains should specify whether the content element contains unconstrained RDF/XML or the abbreviated form of RDF/XML that we present in this guidance. Unconstrained RDF/XML should be indicated with content type "application/rdf+xml" and the abbreviated form should be indicated with "application/xml."

• AI Everybody: review Arthur's guidelines
  • RDF/HTML content for our namespace and property URIs
    • http://open-services.net/pipermail/oslc-core_open-services.net/2010-October/000605.html

Minutes

Attendees and notes from the meeting

Possible Attendees

• DaveJohnson
• SteveSpeicher
• NickCrossley
• ScottBosworth
• JimConallen
• TackTong
• IanGreen

Topics discussed

TBD