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
>
RmHome
>
RmMeetings
>
RmMeetings20110124
(24 Jan 2011,
IanGreen
)
(raw view)
Meeting 24th January 2011 Chair: Ian Apologies: Simon * Welcome to new workgroup participants * Christian Haerdt and Ian Giblett (both of EADS). * V2.0 activities: * Change to spec. regarding oslc.properties. * Awaiting update to RDF / HTML vocabulary on the wiki (Action on Ian). (Cf. OSLCCoreURINamingGuidance.) * Implementation Reports for RM. See [[https://spreadsheets.google.com/ccc?key=0Ak9K8gP9E9OTdGk3WFp5N2NRNkUtMS1aZDlnVV9mRlE&authkey=CIn-3KYC&hl=en_GB#gid=0][OSLC RM 2.0 Implementation Report on Google Docs]]. * Discussion * Relationship to other protocols (STEP/AP, RIF, SysML)being pursued at OSLC PLM workgroup. * Requirements Organization * Feedback from Simon RmRequirementsOrganization. * Scenario Development * Relationship to OSLC RM V2 Collections * Question: Are such resources "fixed" or can they be defined by query? (Eg delegated UI to define query for requirement collections) * Use cases around resource shape * OSLC AM "Link Type" resource model * How would a consumer create a new link type? * How would a consumer create a new resource shape? * Baselines(OSLC AM Context) * Feedback from Simon RmBaselineFeedback Minutes Attendees: IanGreen, Dominic, Simon, IanGiblett, Jim, DaveJohnson Minutes: Jim - what is the impact of oslc.properties. OSLC AM working on MAY, and current implementation is in progress. Question about consistency across OSLC domains. Jim will talk to implementation team about CAM compliance if we move to MUST. Simon: Requirement Organization. These are ordered trees, not graphs. How do requirements which are reused interact via trace relationships? Jim - how does this work with AM resources? Some products could require more than one canonical hierarchical view over a given set of subsidiary resources. Naming of things is important to support some use cases (namespaces). Need to have multiple, parallel hierarchiesw "view" that organize resources. We don't want to make any assumptions that there is one way to organized resoures. Dominic: need to create a resouce without there having to be a canonical place to organize those resources. We want it to be easy to be a provider.
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 - 24 Jan 2011 - 17:00:12 -
IanGreen
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