[OSLC] OSLC QM 1.0 specification

Fri Dec 11 09:31:09 EST 2009

Jim,

In RDF, the data model is a set of triples, and there is no implied 
ordering of the triples. The ordering must be stated explicitly. You could 
define a your own "order" property whose value was an integer. Or you 
could use the built-in properties, rdf:_1, rdf:_2, ... which RDF/XML makes 
easy to use via rdf:li in rdf:Seq.

You could also use XML literal property values where appropriate since 
ordering is significant in XML in general.

Arthur Ryman, IBM DE
Chief Architect, Rational Project and Portfolio Management
Office: 905-413-3077, Cell: 416-939-5063
Assistant: Nancy Barnes, 905-413-4182 

James Conallen/Philadelphia/IBM at IBMUS
12/09/2009 05:37 PM

To
Martin Nally/Raleigh/IBM at IBMUS
cc
community at open-services.net, community-bounces at open-services.net, 
oslc-qm at open-services.net, Paul McMahan/Raleigh/IBM at IBMUS, Arthur Ryman 
<ryman at ca.ibm.com>
Subject
Re: [OSLC] OSLC QM 1.0 specification

When managing multi-valued properties in this way, is ordering implied by 
order in the document?  For example in UML Models of operations, the order 
of parameters of an operation is important.

Inserting new values in a specific position would naturally require the 
entire document to be PUT back, with the new property inserted in the 
correct place.  Or perhaps some other more elaborate mechanism could be 
invented to allow the insertion or deletion of specific values.

<jim/>

jim conallen
jconallen at us.ibm.com
Rational Software, IBM Software Group

From:
Martin Nally/Raleigh/IBM at IBMUS
To:
Paul McMahan/Raleigh/IBM at IBMUS, Arthur Ryman <ryman at ca.ibm.com>
Cc:
community at open-services.net, oslc-qm at open-services.net, 
community-bounces at open-services.net
Date:
12/09/2009 03:08 PM
Subject:
Re: [OSLC] OSLC QM 1.0 specification
Sent by:
community-bounces at open-services.net

This design adopts the design for multi-valued properties documented in 
the CM spec. I don't think this is a good design and we shouldn't 
propagate it. The OSLC estimation workgroup is doing this the "right" way, 
as shown in this example:

<?xml version="1.0"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:ems="http://open-services.net/software-metrics/">
  <ems:Project
     rdf:about="http://braintwistors.example.com/ems/v1.0/Project/4201">
     <dc:title>Tsunami 1.0</dc:title>
     <dc:description>
        The goal of ... 
     </dc:description>
     ...
     <ems:hasEstimate
        rdf:resource="
http://braintwistors.example.com/ems/v1.0/Estmate/4203" />
     <ems:hasEstimate
        rdf:resource="
http://braintwistors.example.com/ems/v1.0/Estmate/4204" />
     ...
     <!-- other properties of this project resource have been omitted for 
brevity -->
  </ems:Project>
</rdf:RDF>

In other words, a multi-valued property is just what it says - a property 
with multiple values, as illustrated here by "ems:hasEstimate". You do not 
introduce a separate collection resource with separate link resources - 
that design is not in the spirit of REST, it's just an old-fashioned OO 
programming API exposed via http.

Best regards, Martin

Martin Nally, IBM Fellow
CTO and VP, IBM Rational
tel: (949)544-4691

Paul McMahan---12/09/2009 12:05:55 PM---The OSLC Quality Management V1 
specification is available at : http://open-services.net/bin/view/Mai

From:

Paul McMahan/Raleigh/IBM at IBMUS

To:

community at open-services.net

Cc:

oslc-qm at open-services.net

Date:

12/09/2009 12:05 PM

Subject:

[OSLC] OSLC QM 1.0 specification

Sent by:

community-bounces at open-services.net

The OSLC Quality Management V1 specification is available at :
http://open-services.net/bin/view/Main/QmSpecificationV1

I would like to thank the Quality Management workgroup members (BigLever,
IBM, Sogeti, and Tieto) for their participation in the workgroup and
contributions to the specification.  The broader OSLC community is invited
to view the specification and provide any feedback in the wiki or via the
oslc-qm at open-services.net mailing list.  The Quality Management V2
specification effort is expected to get underway soon so any feedback on
the V1 specification will be especially valuable.

Best wishes.
Paul McMahan
Rational Quality Management
pmcmahan at us.ibm.com

_______________________________________________
Community mailing list
Community at open-services.net
http://open-services.net/mailman/listinfo/community_open-services.net

_______________________________________________
Community mailing list
Community at open-services.net
http://open-services.net/mailman/listinfo/community_open-services.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20091211/868b9574/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20091211/868b9574/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20091211/868b9574/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20091211/868b9574/attachment-0002.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20091211/868b9574/attachment-0003.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20091211/868b9574/attachment-0004.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20091211/868b9574/attachment-0005.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20091211/868b9574/attachment-0006.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20091211/868b9574/attachment-0007.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20091211/868b9574/attachment-0008.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20091211/868b9574/attachment-0009.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20091211/868b9574/attachment-0010.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20091211/868b9574/attachment-0011.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20091211/868b9574/attachment-0012.gif>