It's all about the answers!

Ask a question

How to find if an artifact has links or not in DNG?


G C (498) | asked Jul 09 '21, 5:28 a.m.

we are fetching links of an artifact but we are not aware whether an artifact has links or not.

Is there any way to find it in DNG?

One answer



permanent link
David Honey (1.8k17) | answered Jul 09 '21, 5:49 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Do you mean outgoing links (those stored in DN), incoming links (stored in other applications linking to a requirement), or both?
For incoming links, since DN does not manage or persist that data, it won't be part of the RDF of a requirement and you would have to query LQE (or LDX) for that data.
For outgoing links, a GET on the requirement should produce RDF that includes the outgoing links for that requirement. You will need to use the Oslc-Core-Version=2.0 header on the GET request.


Comments
G C commented Jul 13 '21, 5:32 a.m.

Thanks for the info... But when a GET on requirement is fetched do we get to know it has outgoing link in below format??


David Honey commented Jul 13 '21, 7:41 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

You inspect the RDF of that fetched requirement to see what statements, if any, are made using the requirement's concept URI. This is as described by the OSLC Requirement Management specification. If you want to know which properties represent relationships, you discover the OSLC resource shape for that artifact (typically referenced by an oslc:instanceShape statement), and then GET that resource shape to examine its declared OSLC properties. See OSLC Core Version 3.0. Part 6: Resource Shape. If you know the predicates of the relationships you are interested in, you can simply look for RDF statements made using those predicates against the requirement concept URI subject.

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.