It's all about the answers!

Ask a question

RPE - Artifact Type URI different between project areas (using same type system)

Glyn Costello (13323) | asked Aug 27 '21, 12:39 p.m.


I'm trying to publish by filtering using a typeURI in the format:


I have got this working, however, The typeURI seems to be different between different Project Areas even though they are using the same Type System. this was achieved by creating the component in the project area then "Import Component Properties" from my template component. 

The Artifact Type definition in the Component Properties have the same artifact name and artifact URI which is in the format:

However, in one Project Area, the TypeURI is _mvyesFHLEeuMrfkR2rtkWQ and in the other it's _bLvB4ldLEeuMrfkR2rtkWQ. 

By using a consistent Type system and URI name space scheme, I was expecting that I could do publishing by "artifact type" across multiple projects without having to specify the typeName AND ProjectURI (just specify typeURI). 

Glyn Costello commented Aug 27 '21, 1:29 p.m. | edited Aug 27 '21, 1:50 p.m.


Thanks, but I can't see how I can publish based on this?

Project A and B both have "Requirement Item" and the same URI = https://server/mlns/dngArtifactType#requirementItem

A GC that uses an RM stream from both these components, how do I "GET" "Requirement Items" for that GC using the REST API scheme below? What value should "typeURI" be?


Geoffrey Clemm commented Aug 27 '21, 1:48 p.m. | edited Aug 27 '21, 1:59 p.m.

It looks like RPE is expecting the UUID of the type as the value of its ?typeURI parameter, which as you've correctly pointed out, differs in every project area.  Have you tried using the URI of the type (the property of the type that you are allowed to set, which actually is a URI)?   If not, we'll need an RPE expert to come up with some suggestion.

One answer

permanent link
David Honey (1.7k17) | answered Aug 31 '21, 4:01 a.m.

A common technique used by applications is to use system-generated type URIs and/or predicate URIs and then use owl:sameAs to associate those URIs with stable external user-defined URIs. See I don't know if that's the case here. Perhaps the reportable REST API supports querying on owl:sameAs ?

Your answer

Register or to post your answer.