| Re: [lyo-dev] Adaptor generator case sensitve? |
|
Yes, it seems to be a bug. Looking at the specs in http://open-services.net/bin/view/Main/RmSpecificationV2, it is clear that the
convention is upper case. I also notice this in the code of the example Bugzilla implementation. Name: Requirement Type URI http://open-services.net/ns/rm#Requirement Could you please report this as a bug (https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Lyo), and assign
it to me? (or just send me the link) In the meantime, you can manually change the two constants TYPE_REQUIREMENT & REQUIREMENT in the class xxxConstants.java? regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45 From: lyo-dev-bounces@xxxxxxxxxxx [mailto:lyo-dev-bounces@xxxxxxxxxxx]
On Behalf Of Jose Manuel Muñoz Hello, We have been using the Adaptor Code Generator in order to support the OSLC specification for our Requirements Management tool (using the 2.0 specification). We have created a resource called Requirements and then generated
the code, but this code generates the resource requirement (lower case). As far as I understand RDF is case sensitive so my question is, is this a bug? This happens also when generating foaf:person resources, that are generated with lower case (instead of
foaf:Person) I’m attaching some examples of the code generated <oslc:ResponseInfo rdf:about="http://xxx.xxx.xxx.xxx:8080/ReqAdaptor/services/serviceProviders/1/resources/Requirement"> <rdfs:member> <oslc_rm:requirement> <dcterms:title rdf:parseType="Literal">Satisfaction</dcterms:title> <dcterms:contributor> <foaf:person> As you can see, both person and requirement are in lower case Thanks in advance Best regards! |