OSLC Core Meeting November 10, 2010

Last week's meeting

Link to OSLC Core spec: OslcCoreSpecification

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

Online meeting:

• For IBM employees, use the following link:
  https://lli.ibm.com/meeting/join/?schedid=4446009 (IBM intranet authentication required)

• For people outside IBM, use the following link:
  https://apps.lotuslive.com/meetings/join?id=4446009

Agenda

Review actions taken since last meeting

• oslc:details is now zero-or-more (Service Provider section) James Conallen pointed out that 'one-or-many' is probably not what we want for an information field. Steve Speicher and I agreed, so I made the change.

• Informative vs. normative issue resolved Defined normative and informative in glossary, with notes on how to recognize each. Marked the introductory section and Appendix C: Links Guidance as informative. Policy is now to use RFC-2119 words to indicate normative passages, and to mark as informative only those informative sections which might be mistaken for normative.

• Tightened normative language of spec Made numerous small changes and tightening of normative wordings, most to clear up places where we were using words like "can" and "is expected to" instead of RFC-2119 terms MAY and SHOULD or MUST.
  • Core spec: revisions 30 - 35
    • http://open-services.net/bin/rdiff/Main/OslcCoreSpecification?rev1=35;rev2=29
  • UI Preview spec: revisions 19 - 20
    • http://open-services.net/bin/rdiff/Main/OslcCoreUiPreview?rev1=20;rev2=18
  • Appendix A: revision 15
    • http://open-services.net/bin/rdiff/Main/OSLCCoreSpecAppendixA?rev1=15;rev2=14
  • Appendix B: revision 12
    • http://open-services.net/bin/rdiff/Main/OSLCCoreSpecAppendixRepresentations?rev1=12;rev2=11
  • Appendix C: revision 7
    • http://open-services.net/bin/rdiff/Main/OslcCoreSpecAppendixLinks?rev1=7;rev2=6

• Delegated UI and UI Preview use CSS 2.1 sizings We weren't being normative, so now say that values MUST be interpreted as in CSS v2.1.

• Added UI Preview to Core spec outline with reference to external doc. Normative spec is essentially this: providers MAY support UI Preview and those that do, MUST do so in accordance with UI preview spec.

Issues for discussion

• Appendix A: Dublin Core: do we want to require specific versions of Dublin Core, FOAF and XSD (for datatypes)?
• Appendix A: Resource Shapes: definition for oslc:isMemberPropery is confusing, should rewrite. Current text:
  • "For the purposes of the OSLC Query Syntax, indicates that the property is used to state membership of a resource in a collection. It is used when you filter a collection resource with a query."
• UI Preview: Provider Responsibilities: why do we say SHOULD rather than MUST for 406 and 200 HTTP status code?
• UI Preview: There is no discovery mechanism other than doing a GET with the right content-type, right?

Minutes

Attendees and notes from the meeting

Attendees

• DaveJohnson
• NickCrossley
• SteveSpeicher
• ScottBosworth

Topics discussed

See above.

Action items:

• Scott B: For size / width in UI preview, don't say "must be interpreted as" say "must be"
• Dave J: For references section, link to specific versions of DC, FOAF and XSD
• Dave J: Propose new header for OSLC specs, something like the one here http://xmlns.com/foaf/spec/
• Dave J: Propose new definition for oslc:isMemberProperty, check with Arthur (and his old emails) for help