NMA is following the httpRange-14 resolution to mint two separate identifiers (with/out a trailing hash) for each entity:
The physical item, e.g. http://nma.conaltuohy.com/object/64620#
The metadata record describing it, e.g. http://nma.conaltuohy.com/object/64620
This should be explained in the API documentation so the significance of the hash is clearer, e.g.
<rdf:Description rdf:about="object/1234#"><crm:P70i_is_documented_in><crm:E31_Document rdf:about="object/1234"><dc:modified>2018-01-01...
NMA is following the httpRange-14 resolution to mint two separate identifiers (with/out a trailing hash) for each entity:
http://nma.conaltuohy.com/object/64620#
http://nma.conaltuohy.com/object/64620
This should be explained in the API documentation so the significance of the hash is clearer, e.g.
<rdf:Description rdf:about="object/1234#"><crm:P70i_is_documented_in><crm:E31_Document rdf:about="object/1234"><dc:modified>2018-01-01
...See: https://en.wikipedia.org/wiki/HTTPRange-14#Use_of_#