[#230] [plugin/oslc] Please fix some properties predicate names in JSON



Detailed description

The status should be encoded, in the JSON output (at least) as what is in OSLC CM V2.

For instance, status should be "oslccm:status" instead of "heliosbt:status".

Also creator may need to be a RDF resource and not a litteral (to be confirmed wrt the specs)

General Information
Submitted by:
Olivier Berger
Date Submitted: 2010-12-13 07:53
Last Modified by: Nobody
Last Modified: 2017-11-02 20:00
Permalink: https://fusionforge.org/tracker/a_follow.php/230
Votes: 0/1 (0%)
Internal Fields
Data Type: Bugs
Assigned to: Sabri LABBENE (labbenes)
State: Open
Priority: 3
Extra Fields
Accepted As Bug
Target Release:
Found in Version:
Follow-up tabs
Message  ↓
Date: 2010-12-17 11:48
Sender: Olivier Berger

What you describe for the creator is linking to an existing resource, but we don't have such, I'm afraid.

So it would probably be better to have an inlined resource, as in http://open-services.net/bin/view/Main/OSLCCoreSpecJSONExamples#Resource

We may have to discuss the details in another channel, though ;)

Date: 2010-12-17 11:35
Sender: Sabri LABBENE

I fixed the status field so that it becomes "oslccm:status" instead of "heliosbt:status". Still the creator and the assigned to which are not yet ressources. For creator, it is dc:creator and is an RDF ressource like this: <dc:creator rdf:resource="http://myserver/users/joe&quot; />

For the "assigned_to" field, I suggest it becomes like: <dc:contributor rdf:resource="http://myserver/users/bob&quot; />

For the severity/priority fields which is currently relying on the helios_bt ontology. I don't see in OSLC-CM ChangeRequest definition anything that fit with severity/priority FF tracker field.

What do you think ?

No attached documents

No related commits.

Field Old Value Date By
ResolutionNone2010-12-17 11:35
SeverityNone2010-12-17 11:35
assigned_tonone2010-12-13 15:23
Olivier Berger

No relations found.