Stream: IG creation
Topic: link errors for uuids in a bundle
Eric Haas (Nov 15 2019 at 15:29):
I getting a bunch of link errors for uuids in a bundle. I don' t remember having to deal with these before.... Do I need to put them in the ignore list?
Grahame Grieve (Nov 15 2019 at 19:11):
where is this?
Eric Haas (Nov 15 2019 at 22:46):
let me clean up the other errors first then I will get back to you.
Eric Haas (Nov 16 2019 at 05:40):
OK I cleaned up the Da Vinci Notification Guide and am trying to show examples of both Message Bundles and profiled resources that aggregate the references within the same bundle....
here is the the source: https://github.com/HL7/davinci-alerts
here is the CI Build: http://build.fhir.org/ig/HL7/davinci-alerts/branches/master/index.html
and the QA report: http://build.fhir.org/ig/HL7/davinci-alerts/branches/master/qa.html
There are four issues I have....
Eric Haas (Nov 16 2019 at 05:44):
- All the uuid are coming up as bad links for the Bundle examples and the Resources examples. how do I fix that for the Bundles. and I am pondering whether and how to show a freestanding example of resource that really should be in a message bundle.
example error
Bundle-admit-notification-message-bundle-01.html#/html/head/body/div/div/div/div/div/div/div/blockquote/p/a at Line 269, column 801 error The link 'urn:uuid:e442c924-df77-47fa-838f-24a8253bbdd4' for "Amy V. Shaw" cannot be resolved
Eric Haas (Nov 16 2019 at 05:46):
- I have two reverse links in the bundle examples , one does not get this error and the other does
Bundle/admit-notification-message-bundle-01: Bundle.entry[7] error Entry isn't reachable by traversing from first Bundle entry"
is for a reverse link,
this one
Bundle/admit-notification-message-bundle-01: Bundle.entry[7] error Entry isn't reachable by traversing from first Bundle entry"
is for a resources that is directly referenced by the MessageHeader?
Eric Haas (Nov 16 2019 at 05:47):
- This error is also confounding me. the id of the contained endpoint is "direct" and is refernced by the Organization.endpoint using "#75"
Bundle/admit-notification-message-bundle-01: Bundle.entry[7].resource.endpoint[0] error ref-1: SHALL have a contained resource if a local reference is provided ( (url: direct; ids: )) [reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))]
I can load up the bundles to the reference server and not get any errors. So I suspect the profiles
Eric Haas (Nov 16 2019 at 05:48):
- I don't understand what this error means:
MessageHeader/admit-notification-messageheader-01: MessageHeader.focus[0] error Profile based discriminators must have a type with a profile (MessageHeader.focus:admit-notification)
I suspect is because its a freestanding resource and is validated against a profile that aggregates the references to profiles.... I don't get it in the bundle example. So I am pondering whether and how to show a freestanding example - I can ignore the error and document that the example is invalid.
Eric Haas (Nov 16 2019 at 05:48):
oh and there is a 5....
Finally my ig.xml gives errors on the dependency paths. I think those are the correct path since the IG resolves to the resources. Is that a known issue?
Grahame Grieve (Nov 16 2019 at 15:31):
in my queue, but probably not till some time on Monday
Eric Haas (Nov 16 2019 at 19:13):
TY...not a huge rush on my end but I thought I'd deal with these issues early rather than last minute.
Eric Haas (Dec 02 2019 at 17:45):
@GG Ping on error 1 above. #2 discussed on another thread. 3 - 5 can wait until 1 is resolved.
Grahame Grieve (Dec 02 2019 at 17:46):
#1 is still happening?
Eric Haas (Dec 02 2019 at 19:18):
Thanks 1-3 are is fixed... now my question is for #4 these examples are essentially bundle "entries" and retain the UUIDS outside the bundle and this leads to a link error. .... What is the best way to show and example resources for a profile that defines ( aggregates) other resources inside the same bundle? :
- link to the bundle?
- highlight the resource within the bundle by displaying the bundle as an inline code block.
- link to the resource example as an invalid example ( and document is invalid as a freestanding resource )?
@Lloyd McKenzie
Eric Haas (Dec 02 2019 at 19:21):
5 is fixed as well - thanks
Lloyd McKenzie (Dec 02 2019 at 23:10):
@Eric Haas, to clarify, you have an example Bundle and you want to be able to link to resources inside the Bundle from your documentation?
Eric Haas (Dec 02 2019 at 23:16):
I have profile that define a reference as aggregrating inside the same bundle. That resource can not stand alone and validate sinceit and the referenced resource are not in a Bundle. So providing an example of a valid profile instance is problematic. I don't want to bury it in a complete bundle and it is invalid as a stand alone resource instance.
Lloyd McKenzie (Dec 02 2019 at 23:52):
Ah. So you want an instance with known validation errors and want to be able to suppress those. That could theoretically be a rationale for allowing suppressing of errors, but it would be easy for it to be abused. The alternative is to have the whole example as a valid Bundle but be able to render excerpts of the Bundle. That's my preference because then you could point to the whole Bundle so readers could see the fragment in context and you'd know for sure that your overall instance was in fact valid
Eric Haas (Dec 03 2019 at 00:06):
Is there a way to render excerpts beside using code blocks and manually editing the content?
Lloyd McKenzie (Dec 03 2019 at 00:09):
Not yet, but it's on my list of features I'd like to add to the tooling. I have a sense of how to do it for XML. JSON would be harder. (Not having comments really sucks...)
Grahame Grieve (Dec 03 2019 at 01:03):
It's on my list to be able to have known bad examples in an IG
Grahame Grieve (Dec 03 2019 at 01:04):
both deliberately bad, and also packagingly bad.
Alexander Henket (Feb 16 2020 at 06:49):
@Grahame Grieve I'm getting the same errors today although it appears from reading this thread these were supposed to be solved? The IG Publisher reports linking errors for all Bundles that have internal uuid or oid based links.
Bundle-XXX-Jangi-910.html#... at Line 159, column 365 error The link 'urn:uuid:e89d404f-428e-11ea-7656-020000000000' for "I. XXX_Jangi" cannot be resolved
There are also some odd ones like these:
Bundle-XXX-Jangi-910.html#... at Line 820, column 30 error The link 'tel:+31612345678' for "+31612345678" cannot be resolved
In case you want to test:
Grahame Grieve (Feb 17 2020 at 00:57):
thanks - fixed next release
Last updated: Apr 12 2022 at 19:14 UTC
