Messages

1

PCS Suggestions and Requests / Re: Change the parent of a resource via PCS OSLC

« on: June 27, 2023, 03:28:46 pm »

I tried the following to post to `<protocol>://<server>/<model_name>/oslc/am/pu/resource/`

```xml
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:oslc_am="http://open-services.net/ns/am#"
                xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
                xmlns:dcterms="http://purl.org/dc/terms/"
                xmlns:foaf="http://xmlns.com/foaf/0.1/"
                xmlns:ss="http://www.sparxsystems.com.au/oslc_am#">

     <oslc_am:Resource>
          <!--Required Property-->
          <dcterms:identifier>el_{5FE6EEBA-20C4-4fae-804E-6076C72C7D32}</dcterms:identifier>
          <ss:useridentifier>{C3EE2FC5-D661-4886-BA90-E805B41C521C}</ss:useridentifier>
          <!--Updateable Properties-->
          <ss:parentresourceidentifier>pk_{9A699728-DB95-4126-A142-DE084597EE82}</ss:parentresourceidentifier>
     </oslc_am:Resource>

</rdf:RDF>
```

but got 400 response:

```xml
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:oslc="http://open-services.net/ns/core#">
    <oslc:Error>
        <oslc:statusCode>400</oslc:statusCode>
        <oslc:message>Invalid property 'ss:parentresourceidentifier'</oslc:message>
    </oslc:Error>
</rdf:RDF>
```

Other updateable properties such as `dcterms:title` can be updated as expected.

Is there a workaround for changing the parent?

2

PCS Suggestions and Requests / Change the parent of a resource via PCS OSLC

« on: June 23, 2023, 02:33:42 pm »

Trying to use OSLC to move an element or a package to a different place, but there’s no documentation for updating a resource’s parent (based on https://sparxsystems.com/enterprise_architect_user_guide/16.1/the_model_repository/oslc_upd_resources.html and the examples). The updating operation only deals with its listed features internally, so I cannot find a way to move it to a different place (e.g, move it one level up in the tree structure).
 
1. When creating a new resource, the `ss:parentresourceidentifier` is required. Is there an optional one where we can use to specify the parent location in updating operation?
2. `ss:parentresourceidentifier` is in the http://model/oslc/am/rs/cfresouce (resource shape for create) but not in http://model/oslc/am/resource (resource shape for update)
3. If not, is there workaround to get the same effect for moving a resource (preserving the relationships and all properties etc of the item being moved)?

If OSLC supports updating resource's parent, the workflow can be more automated and easily integrated.

Thank you!

3

Bugs and Issues / Can't create tagged values via OSLC

« on: May 19, 2023, 06:04:33 pm »

Short description of issue: I can not create a tagged value for a package or element based on the OSLC documentation. The similar error messages appear when I use the creation factory endpoints to create a discussion. However, I can create a new element or package, and update the tagged value once it's created.

PCS version is 5.1.123 iirc and OS is Windows10 Enterprise

The error message:

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:oslc="http://open-services.net/ns/core#">
    <oslc:Error>
        <oslc:statusCode>400</oslc:statusCode>
        <oslc:message>'ss:taggedvalue' is not a valid Enterprise Architect Creation Factory Resource</oslc:message>
    </oslc:Error>
</rdf:RDF>

Io check the service provider info from http://<modelname>/oslc/am/sp/ and can see that the taggedvalue is indeed in the oslc:CreationFactory which should not result the error message above.

Any advice is appreciated!