It's all about the answers!

Ask a question

Custom RDF URI (DNG) vs RDF Vocabulary (LQE)

David Reilly (69642) | asked Nov 09 '18, 10:05 a.m.


We are trying to use custom artifact types and link types.

We notice that there is a Custom RDF URI label on artifact, attributes, data types, and link types within the RM application. This seems to have some impact on LQE / JRS, and provides a bit of a shortcut with custom sparql / merged types.

However, we also noticed that in the LQE Administrative area, there is a Vocabulary section which allows you to upload XML for a custom RDF, alongside all other RDFs capable of being used in DNG. Does this mean that in order for us to use our Custom RDFs, they need to be defined in the vocabulary as well?

Just as a note, we are also trying to use these with the OSLC API. Unsure if this makes a difference or not. 

Would greatly appreciate anyone who can shed some light on this distinction. 


One answer

permanent link
Geoffrey Clemm (30.1k33035) | answered Jun 06 '19, 8:38 a.m.
edited Jun 06 '19, 8:38 a.m.

My understanding is that adding the XML for a custom RDF URI is optional, so you can introduce a custom RDF URI without defining/uploading an XML vocabulary for that custom RDF URI.

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.