Update the excluded list-building to ignore attribute-only nodes if that parent is captured somewhere else?

[roomthily]

That is not quite right. It would be ignore the entire element if some piece of the element was extracted and we don't care about the rest? Realistically, "simple" here is not important.

<DCPType>
    <HTTP>
        <Get>
            <OnlineResource xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://egisws02.nos.noaa.gov/ArcGIS/services/NMFS/EFHAreasProtectedFromFishing/MapServer/WMSServer"/>
        </Get>
    </HTTP>
</DCPType>

Better alternative - if an ontology-driven value is an attribute and the parent element contains other attributes, just capture related?

Turtles and overthinking.

[roomthily]

Ignoring the example where we aren't really concerned about the "simple" value, there could be cases where we are capturing one attribute for the explicit triples but not other attributes on that same element. So we don't want to later skip that element and its other attributes for the "remainders" block. We lose that relationship in the triplestore, though.