1. I should add that the examples chosen are PCA RDL examples, and they are in
http://posccaesar.org/rdl namespace. And yes, it is proposed to change to human-readable ID as main URI.
2. PCA has several endpoints. The development endpoint that has implemented ID spec examples is currently available from: human access
http://posccaesar.org/development , for machines
http://posccaesar.org/development/sparql . The production endpoint for the PCA RDL is accessible from
http://posccaesar.org/endpoint/ (human access) and
http://posccaesar.org/endpoint/sparql (machines) and resources have not been changed.
3. Actually, you can view data about the MannedContainer resource from
http://posccaesar.org/dev/data/Pump?output=xml A different seralization is used, but yes, MannedContainer will be the ID of that resource.
4. No, the spec proposes to change to human-readable ID as main URI and have the RDSnnnn/Rnnnnn/R-UUID at the end of a predicate
5. An implementation of the JORD ID spec on the resource
http://posccaesar.org/rdl/RDS327239 existing today in the RDL would result in
http://posccaesar.org/rdl/Pump .
http://posccaesar.org/dev/Pump is an example resource in a different namspace than the one used for the PCA RDL, and should not be referenced to and can not be considered stable.
http://posccaesar.org/development/Pump is not a resouce and is not planned to be a resource.
http://posccaesar.org/development/ is the endpoint address and to avoid confusion a different namespace is used.
6. Currently there are no ISO references as such in the PCA RDL, but that might change.