Marklogic semantics: treatment of rdf:about attribute values -

i trying import rdf data source (rdf/xml) marklogic 8.02 mlcp 1.3.3.

during import, swamped warnings one:

15/06/29 15:03:58 warn contentpump.rdfreader: 57fad317-4744-4f88-a8f7-6c21c662ad08.rdf: {w107} bad uri: code: 45/unregistered_nonietf_scheme_tree in scheme: scheme name has "-" in it, not start in "x-" , prefix not known prefix of alternative tree uri schemes.

looking @ source data (rdf/xml), caused statements this:

<rdf:description
rdf:about="rvr-jurisprudentie:http%3a%2f%2flinkeddata.overheid.nl%2fterms%2fjurisprudentie%2fid%2fecli%3anl%3arvs%3a2013%3a549:http%3a%2f%2flinkeddata.overheid.nl%2fterms%2fbwb%2fid%2fbwbr0005181%2f2986364%2f2015-01-01%2f2015-01-01">

so looks ml thinks rdf:about attribute contains uri , complains not valid one.

so 3 questions:

1. why ml think has uri. haven't encountered problem other toolsets.
2. is there switch ignore warnings (piping output in terminal doesn't seem work)
3. does have further effects down road (i.e. performance etc.)?

why ml think has uri. haven't encountered problem other toolsets.

because rdf/xml syntax specification says:

aboutattr =        attribute rdf:about {            uri-reference        } 

the rdf:about attribute expects receive uri , data have looks uri in attribute:

rvr-jurisprudentie:http%3a%2f%2flinkeddata.overheid.nl%2fterms%2fjurisprudentie%2fid%2fecli%3anl%3arvs%3a2013%3a549:http%3a%2f%2flinkeddata.overheid.nl%2fterms%2fbwb%2fid%2fbwbr0005181%2f2986364%2f2015-01-01%2f2015-01-01 

it using custom uri scheme doesn't conform rfc 3986 generic uri syntax , marklogic issues warning. it still valid uri if 1 can't interpreted some/all tooling.

is there switch ignore warnings (piping output in terminal doesn't seem work)

there not appear one, in marklogic content pump documentation show enabling debug level messages:

edit file mlcp_install_dir/conf/log4j.properties. example, if mlcp installed in /opt/mlcp, edit /opt/mlcp/conf/log4j.properties. in log4j.properties, set properties log4j.logger.com.marklogic.mapreduce , log4j.logger.com.marklogic.contentpump debug. example, include following:

log4j.logger.com.marklogic.mapreduce=debug log4j.logger.com.marklogic.contentpump=debug 

obviously opposite of want since log4j configuration can turn down logging error in same way can turn debug shown in example.

does have further effects down road (i.e. performance etc.)?

you may have problems if need pass data other rdf or sparql tools interpret uri specification more strictly