[from JG's 2009-12-04 email] What capability do you want added or improved? API to modify a term's fields (definition, comments, whatever) Where do you want this capability to be accessible? In the main ORR service What sort of input/command mechanism do you want? An HTTP POST call where I can provide:
username/password
Ontology URI
the URI of the term to be modified
values for the term's properties What is the desired output (content, format, location)? A textual response (perhaps in XML) indicating the result of the operation:
i) success, confirming the modification and the term URI; ii) error,
including the reason of the error.
Other details of your desired capability?
0) In contrast with issue #231 (addition of a new term), the modification
of an existing term does seem to require the creation of a new version of
the vocabulary.
1) An HTML form should be included to illustrate the required information
(and demonstrate the functionality).
2) A programmatic example (in java) showing how to use the service.
From caru...@gmail.com on December 13, 2009 15:33:36
[from JG's 2009-12-04 email] What capability do you want added or improved? API to modify a term's fields (definition, comments, whatever) Where do you want this capability to be accessible? In the main ORR service What sort of input/command mechanism do you want? An HTTP POST call where I can provide:
Other details of your desired capability?
0) In contrast with issue #231 (addition of a new term), the modification of an existing term does seem to require the creation of a new version of the vocabulary.
1) An HTML form should be included to illustrate the required information (and demonstrate the functionality).
2) A programmatic example (in java) showing how to use the service.
See related: #231, #214
Original issue: http://code.google.com/p/mmisw/issues/detail?id=232