David Waltermire

This appears to relate to the [port range constraint](https://github.com/usnistgov/OSCAL/blob/f159b28948cb0034370fb819a45bfdaeaef5192a/src/metaschema/oscal_implementation-common_metaschema.xml#L318) in OSCAL. The `<` entity used might be causing the issue. We need to investigate this.

FWIW, the `has-oscal-namespace` function is not implemented in Metapath. This is an [extension supported](https://github.com/usnistgov/liboscal-java/blob/main/src/main/java/gov/nist/secauto/oscal/lib/metapath/function/library/HasOscalNamespace.java) in liboscal-java. There is also a [`resolve-profile`](https://github.com/usnistgov/liboscal-java/blob/main/src/main/java/gov/nist/secauto/oscal/lib/metapath/function/library/ResolveProfile.java) function. I believe `has-oscal-namespace` could be eliminated by replacing...

Given that there has been no additional feedback around adding support for specific tags based on option 2, I am going to close this issue. We can reopen this if...

@aj-stein-nist Can you confirm that develop has been updated to point to the latest Metaschema submodule commit?

@arjun2 I am seeing the same. This is [example 415](https://spec.commonmark.org/0.30/#example-415) from the [CommonMark specification](https://spec.commonmark.org/0.30/). A parser creates the following AST: ``` Document[0, 16] Paragraph[0, 16] Text[0, 15] chars:[0, 15, "foo**...

Tracing this, I believe the problem relates to the code at: https://github.com/vsch/flexmark-java/blame/cc3a2f59ba6e532833f4805f8134b4dc966ff837/flexmark/src/main/java/com/vladsch/flexmark/parser/internal/InlineParserImpl.java#L1418 It looks like the loop [here](https://github.com/vsch/flexmark-java/blame/cc3a2f59ba6e532833f4805f8134b4dc966ff837/flexmark/src/main/java/com/vladsch/flexmark/parser/internal/InlineParserImpl.java#L1424) is rewinding the stack to find the outer most opener and closer....

@vsch Is there a possibility of prioritizing a fix? I am not sure I am able to fully debug this to create a PR or I would.

> @vsch Is there a possibility of prioritizing a fix? I am not sure I am able to fully debug this to create a PR or I would. I was...

#1023 requests the addition of an `imported-from` link rel, which can address the need here.

This could take advantage of prop/link grouping (#1064) to express a link/prop pair to point the component definition (using `imported-from`) and identify the specific component by UUID using a prop...