Some questions about the REST API
Hello,
I am developing an application that utilizes the REST API for RTC. However, I am having a small issue understanding how to utilize the creation of a draft work item. I am confused about there being multiple ways to represent a type in the JSON representation. For example,
rdf:type, rtc_cm:type and dc:type
They all seem to mean the same thing, but I don't think they are interchangeable. My application also has no way of updating the user as to which fields are required to create a work item, so there is no way for me to create an actual work item. A draft is my only option.
So, in order to determine if a type is valid. I am going to have to let the user type in a String and then validate to make sure that the type is valid. I don't think doing this for every potential field in a work item, is a good idea.
This brings me to my next question. How customizable is the RTC environment? Can the representation of a work item, a normal one or a draft, be drastically different depending on the environment?
Thanks for any responses. It will help greatly to clear some of these up
Accepted answer
I'm going to try to give you some pointers that came from searching in the Jazz.net forum and general Google. I'm not sure how to answer all your questions but there is a way to understand what rtc_cm: vs dc: mean?
In this article, https://jazz.net/library/article/352, Steven explains that attributes that use dc: or oslc_cm namespace are defined by OSLC CM specification and CORE specification:
http://open-services.net/bin/view/Main/OslcCoreSpecification
http://open-services.net/bin/view/Main/CmSpecificationV2
There is also this article on how to use the plain Client API for RTC: https://jazz.net/library/article/1229
It is also possible to create a workitem via the OSLC API. THere should be a way to determine what attributes are required to create a workitem via plain Client API or OSLC.
You can also consider using the delegated UI concept of the OSLC API. See https://jazz.net/library/article/352 RTC as a OSLC provider makes available a "delegated creation" dialog that you can make use of in your application as an OSLC consumer.
I am not sure why you make a d
One other answer