This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.

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:

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.

  • 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

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
Topic revision: r7 - 16 Nov 2010 - 19:16:40 - DaveJohnson
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback