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.

Reporting Meeting, 2010-03-29


See Reporting Meetings for meeting logistics.

Agenda and Minutes

Agenda

1. Update on outstanding actions
2. Core Spec WG Review

  • Hello Core WG team,

    I'm done with my edits on the Core spec draft for now and we're ready
    for another thorough review. I finished everything except for the Atom
    and Turtle representation rules. I integrated Steve Speicher's work on
    Service Providers and Delegated UI with some small changes. I also
    added in the Query Syntax work, though I'm not sure Arthur is 100%
    done.

    Here is the current draft:
    http://open-services.net/bin/view/Main/OSLCCoreSpecDRAFT

    Here is the list of issues raised and resolutions to each:
    http://open-services.net/bin/view/Main/OslcCoreV2Issues

    Meeting telecon numbers, passcode and on-line meeting information is here:
    http://open-services.net/bin/view/Main/OslcCoreMeetings

    Here's the slightly revised schedule for next week's meetings. Note
    that Resource Shapes and Query is now on Tuesday afternoon instead of
    morning.

    (times are US Eastern)

    Monday March 29
    10AM - Noon
    - Overall comments
    - OSLC defined resources
    - Common properties
    1:30PM - 3:30PM
    - Service Resources
    - Delegated UI

    Tuesday March 30
    10AM - Noon
    - Representations
    - Authentication
    1:30PM - 3:30PM
    - Resource Shapes
    - Query
3. Paging

4. Resource Collection Shape

  • RESOLVED The conceptual model in the Query Resource section does not clearly state how a query result would be represented in the data model. So far, it only states that Query Resource has properties rdf:type and dc:title. Need to describe a data model of how a Query Resource would be resulted from a query of a collection of resources of the same type. In additional, an example of a conceptual model of Query Resource, a query, and its resultset plus applying the RDF/XML representation rule to arrive at a RDF/XML representation of the resulted Query Resource would be greatly helpful. (TackTong, 03/19/2010)
    • Response We now specify a Query Resource in OSLC Defined Resource terminology and have specific rules for how it is represented (03/26/2010)
  • <rdf:RDF 
    xmlns:oslc="http://open-serivces.net/"
    xmlns:oslc_cm="http://open-serivces.net/cm"
    xmlns:oslc_fm="http://open-serivces.net/fm"
    xmlns:oslc_rm="http://open-serivces.net/rm"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:dc="http://purl.org/dc/elements/1.1/">

    <oslc:Query rdf:about="http://example.com/query?oslc%3Aquery=remote" >
    <dc:title>Query results for term 'remote'</dc:title>
    <oslc:nextPage rdf:resource="http://example.com/query?oslc%3Aquery=remote,page=2"/>
    <!-- other properties here... -->
    </oslc:Query>

    <oslc_cm:ChangeRequest rdf:about="http://example.com/data/9D764F35AD1">
    <dc:title>Password protect the remote control panel</dc:title>
    <!-- other properties here... -->
    </oslc_cm:ChangeRequest>

    <oslc_rm:Requirement rdf:about="http://example.com/data/9D764F35777">
    <dc:title>Build a remote control panel</dc:title>
    <!-- other properties here... -->
    </oslc_rm:Requirement>

    <oslc_fm:FooReport rdf:about="http://example.com/data/9D764F3534F">
    <dc:title>Remote Control Firmware Foo Measurement Report</dc:title>
    <!-- other properties here... -->
    </oslc_fm:FooReport>

    </rdf:RDF>

Outstanding Action Items

Minutes

Attendees: JamesMoody, PaulMcMahan, GaoWeibin, XiangDongHu, SteveSpeicher, PaulTasillo? , BenjaminWilliams, SebRose

Regrets: VishyRamaswamy, DaveJohnson, ArthurRyman, JoanTouzet

1. The WG was made aware of the Core Spec Draft and the review schedule this week. Reporting WG members are encouraged to comment on the Core Spec Draft and attend review sessions.

2. The Paging section of the Core Spec. was discussed and concluded sufficient for Reporting.

  • An indicator for Unstable or Stable Paging was discussed and concluded not needed for now.
  • A client specified maximum page size was discussed and concluded not needed for now.

3. An example for a Query Resource with a collection of resources was extracted from Core Spec. for reference and discussion.

Next Week

  • OSLC Reporting Specification

Comments

Add your comments here:

 
Topic revision: r6 - 23 Aug 2011 - 13:36:34 - SteveSpeicher
 
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