[OSLC-ArchMgmt] [OSLC-RM] Suggestions for link resource

Wed Oct 28 03:43:36 EDT 2009

I agree with the principles in Jim's suggestions, but have a couple of
observations / clarifications.

a.       You sensibly suggest that we provide information on the most
recent modifier of the resource, and you propose doing this via a
dc:contributor element.  Using this element bends its definition a bit
(Dublin Core defines dc:contributor as 'an entity responsible for making
contributions to the resource' as opposed to 'the most recent entity
that made contributions to the resource').  This is the closest that
Dublin Core comes to defining the last modifier, so the question is one
of general principle - are we happy to infer meaning to DC metadata
elements in the OSLC-RM context which isn't present in their DC
definition?

b.      Have I understood your proposals about creator/modifier elements
correctly?  I think you are suggesting that the resource creator and
modifier can be described as (i) free form text, (ii) an rdf:resource
URI to a person resource, or (iii) an inline FOAF definition of the
person.  Is this right? (I would agree)

Simon

From: oslc-rm-bounces at open-services.net
[mailto:oslc-rm-bounces at open-services.net] On Behalf Of James Conallen
Sent: 27 October 2009 20:24
To: James Conallen
Cc: oslc-rm at open-services.net; oslc-am at open-services.net;
oslc-am-bounces at open-services.net
Subject: Re: [OSLC-RM] [OSLC-ArchMgmt] Suggestions for link resource

I'd like to amend to this another option for specifying the
creator/modifier of a resource link We can also permit the use of the
FOAF vocabulary:

<dc:creator rdf:resource="https://liz:9443/users/adam">
<foaf:Person>
<foaf:name>Adam Administrator</foaf:name>
<foaf:mbox rdf:resource="mailto:adam at example.com" />
<foaf:img rdf:resource="https://liz:9443/users/adam/photo" />
</foaf:Person>
</dc:creator>

<jim/>

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

 James Conallen---10/26/2009 11:33:56 PM---Looking over the details of
the link resource currently proposed for OSLC RM (and currently suggeste

From:

James Conallen/Philadelphia/IBM at IBMUS

To:

oslc-rm at open-services.net, oslc-am at open-services.net

Date:

10/26/2009 11:33 PM

Subject:

[OSLC-ArchMgmt] Suggestions for link resource

Sent by:

oslc-am-bounces at open-services.net

--------------------------------------------------------------------------
Simon Wills
Managing Director
integrate systems engineering ltd
m: +44 (0)7967 091824
t: +44 (0)1225 859991
f: +44 (0)1225 859993
e: simon.wills at integrate.biz
w: http://www.integrate.biz/
--------------------------------------------------------------------------

________________________________

Looking over the details of the link resource currently proposed for
OSLC RM (and currently suggested for OSLC AM as well). I have some minor
changes I'd like to propose. 
First, is to make a distinction between the original creator of a
resource, and the most recent modifier of it. The Jazz storage services
currently make this information available, and use these DC terms for
them. 

Also instead of allowing free form creators and dates, we say that a
creator or contributor can be referenced with a URI,

<rdf:RDF 
xmlns:oslc="http://open-services.net/xmlns/common/1.0/
<http://open-services.net/xmlns/common/1.0/> " 
xmlns:dc="http://purl.org/dc/terms/ <http://purl.org/dc/terms/> "
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#
<http://www.w3.org/1999/02/22-rdf-syntax-ns> "

<oslc:Link rdf:about="http://www.example.com/resources/links/link1
<http://www.example.com/resources/links/link1> ">
<rdf:subject rdf:resource="
http://www.example.com/resources/requirement55
<http://www.example.com/resources/requirement55> " />
<rdf:object rdf:resource="http://www.example.com/resources/workitem24
<http://www.example.com/resources/workitem24> " />
<rdf:predicate rdf:resource="http://www.example.com/types/implementedBy
<http://www.example.com/types/implementedBy> " />

<dc:creator rdf:resource="http://example.com/users/developer1
<http://example.com/users/developer1> " />
<dc:created rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime
<http://www.w3.org/2001/XMLSchema#dateTime> ">
2009-10-20T19:49:47-04:00
</dc:created>

<dc:contributor rdf:resource="http://example.com/users/admin1
<http://example.com/users/admin1> " />
<dc:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime
<http://www.w3.org/2001/XMLSchema#dateTime> ">
2009-10-20T19:49:47-04:00
</dc:modified>

</oslc:Link>
</rdf:RDF>

or allow the use of FOAF vocabulary (second example)

<rdf:RDF 
xmlns:oslc="http://open-services.net/xmlns/common/1.0/
<http://open-services.net/xmlns/common/1.0/> " 
xmlns:dc="http://purl.org/dc/terms/ <http://purl.org/dc/terms/> "
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#
<http://www.w3.org/1999/02/22-rdf-syntax-ns> "

<oslc:Link rdf:about="http://www.example.com/resources/links/link1
<http://www.example.com/resources/links/link1> ">
<rdf:subject rdf:resource="
http://www.example.com/resources/requirement55
<http://www.example.com/resources/requirement55> " />
<rdf:object rdf:resource="http://www.example.com/resources/workitem24
<http://www.example.com/resources/workitem24> " />
<rdf:predicate rdf:resource="http://www.example.com/types/implementedBy
<http://www.example.com/types/implementedBy> " />

<dc:creator rdf:resource="http://example.com/users/developer1
<http://example.com/users/developer1> ">
<foaf:name>Dan Developer</foaf:name>
<foaf:mbox rdf:resource="mailto:admin1 at example.com
<mailto:admin1 at example.com> " />
<foaf:img rdf:resource="http://example.com/users/developer1/photo
<http://example.com/users/developer1/photo> "/>
</dc:creator>
<dc:created rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime
<http://www.w3.org/2001/XMLSchema#dateTime> ">
2009-10-20T19:49:47-04:00
</dc:created>

<dc:contributor rdf:resource="http://example.com/users/admin1
<http://example.com/users/admin1> ">
<foaf:name>Adam Administrator</foaf:name>
<foaf:mbox rdf:resource="mailto:admin1 at example.com
<mailto:admin1 at example.com> " />
<foaf:img rdf:resource="https://example.com/users/admin1/photo
<https://example.com/users/admin1/photo> "/>
</dc:contributor>
<dc:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime
<http://www.w3.org/2001/XMLSchema#dateTime> ">
2009-10-20T19:49:47-04:00
</dc:modified>

</oslc:Link>
</rdf:RDF>

<jim/>

jim conallen
jconallen at us.ibm.com
Rational Software, IBM Software Group
_______________________________________________
OSLC-AM mailing list
OSLC-AM at open-services.net
http://open-services.net/mailman/listinfo/oslc-am_open-services.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-am_open-services.net/attachments/20091028/aa20b5c0/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 105 bytes
Desc: image001.gif
URL: <http://open-services.net/pipermail/oslc-am_open-services.net/attachments/20091028/aa20b5c0/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 168 bytes
Desc: image003.png
URL: <http://open-services.net/pipermail/oslc-am_open-services.net/attachments/20091028/aa20b5c0/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 166 bytes
Desc: image004.png
URL: <http://open-services.net/pipermail/oslc-am_open-services.net/attachments/20091028/aa20b5c0/attachment-0001.png>