OSLC Core Meeting November 3, 2010
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
Online meeting:
Agenda
Review actions taken since last meeting
AI Dave: propose way to mark sections as normative and informative. Proposal is to add these terms to the OSLC Core Spec glossary and then mark sections as "(this section is informative)" or "(this section is normative)".
- Normative. Setting forth requirements that must be met to establish conformance with this standard; or providing recommendations or optional courses of action. For recommended or optional features, conformance is not dependent on the fact of implementation, but, if implemented, that implementation is as prescribed in this standard. Contrast with informative. Notes within a normative section may be informative.
- Informative. Supplying background or explanation. Contrast with Normative.
Other issues
Some issues found in recent reviews:
- IRI vs. URI
- Is a resource shape allowed to define new required properties not in spec resource definition?
- Do we really want DateTime? to be ISO 8601 (what we use now) vs. RFC-3339 (what Atom uses)?
- oslc.properties section: need to explain term "property tree pattern"
- Need to mention escaping in oslc.properties section?
- In delegate UI section, do we need to say size hints MUST use CSS 2.1?
Minutes
Attendees and notes from the meeting
Possible Attendees
Topics discussed
TBD
Topic revision: r2 - 03 Nov 2010 - 02:24:19 -
DaveJohnson