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
.
TWiki
>
Main Web
>
OslcCore
>
OslcCoreMeetings
>
OslcCoreMeetings05192010
(21 May 2010,
DaveJohnson
)
(raw view)
---+ OSLC Core Meeting May 19, 2010 ---++ 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 Probably a short meeting today Quick review of status * About 10 open issues on the issues page, about 5 need discussion * Partial Update proposal under review * [[OslcCorePartialUpdate]] current draft * Link Guidance coming this week How you can help * Specification is ready for some real proof-reading, please pitch in * Review the RESOLVED issues on the issues page, did we resolve your issues to your satisfaction? * Review the Partial Update proposal and give feedback on the mailing list Current open issues * OSLC Defined resources * 21. %RED%OPEN%ENDCOLOR% No need for NLS string, any string should able to be an NLS string * 22. %RED%OPEN%ENDCOLOR% Jim Conallen questions Core's stance on "discard unknown property values" saying that we cannot expect a domain to "define all possible types of file resources it is allowed to version?" * Response: No change, opaque resources should be created via special creation factory * Service Provider * 25. %GREEN%OPEN%ENDCOLOR% Use dc:publisher in stead of dc:contributor here * Response: yes, fix this * Query * 22. %RED%OPEN%ENDCOLOR% Proposal to defier oslc.from, oslc.offset, etc. * Response: pending Steve's use cases * Resource Shapes * 19. %GREEN%OPEN%ENDCOLOR% Resource Shape value-types wrong, don't match those in defined resources section * Response: fix this * 20. %GREEN%OPEN%ENDCOLOR% Default property value should be same type as property value itself * Response: fix this * 21. %GREEN%OPEN%ENDCOLOR% allowedValues needs work, should be resource or inline * Response: fix problems but don't add min/max * JSON * 4. %RED%OPEN%ENDCOLOR% Can we remove namespace definitions since we have them in service provider? * Turtle * 1. %RED%OPEN%ENDCOLOR% Need Turtle representation rules, probably just a paragraph ---++ Meeting Minutes Possible Attendees * DaveJohnson * RobertElves * AlainPicard * ArthurRyman * ScottBosworth * NickCrossley * PaulMcMahan We discussed the open issues above. Here are some highlights of the discussion: On NLS strings, we have consensus that the NLS String value type should be dropped On the issue of query resource paging parameters, we had an inconclusive discussion, but Arthur made the point that these parameters are optional and therefore do not place a burden on implementations. Issue: what page info should be in responseInfo: Arthur says put them all in the Response Info because, and they're all optional. We also talked about the need for a separate Common Properties document that is separate from the Core and can grow over time, but did not come out with a definitive proposal for how things should be structured. We talked about the need for caution when domains start to define properties outside of their own namespace, in place where there could be conflict with other domains.
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r2 - 21 May 2010 - 17:39:15 -
DaveJohnson
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
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