Cannot obfuscate xsd:anyURI literals and error parsing the obfuscation configuration

[Duane Holt]

I managed to obfuscate data once, and noticed that the command did not obfuscate xsd:anyURI literals. While I was trying to build sample data to reproduce the problem, the command stopped working altogether. My config file and sample data are attached. Even the exact command which succeed now fails with the same parsing error message.

Here are the commands I used and their output:

$ stardog-admin --server snarl://localhost:myPort db create -n obfDb obfDb.owl
Bulk loading data to new database.
Parsing triples: 100% complete in 00:00:00 (4 triples - 0.4K triples/sec)
Parsing triples finished in 00:00:00.012
Creating index: 100% complete in 00:00:00 (0.8K triples/sec)
Creating index finished in 00:00:00.006
Computing statistics: 100% complete in 00:00:00 (1.3K triples/sec)
Computing statistics finished in 00:00:00.003
Loading complete.
Inserted 4 triples in 00:00:00.113 at 0.0 triples/sec
Bulk load complete.  Loaded 4 triples from 1 file(s) in 00:00:00 @ 0K triples/sec.

Successfully created database 'obfDb'.

$ stardog data obfuscate -c obfConfig.ttl snarl://localhost:myPort/obfDb result.trig
There was an error parsing the obfuscation configuration for the export

Thanks,
Duane

[Evren Sirin]

On Wed, May 21, 2014 at 7:07 PM, Duane Holt <duane....@gmail.com> wrote:

I managed to obfuscate data once, and noticed that the command did not obfuscate xsd:anyURI literals.

That's correct. Right now only string literals are obfuscated and this cannot be changed via the configuration file. The way values are obfuscated right now would create invalid typed literals (e.g. integers would me mapped to arbitrary strings). The xsd:anyURI is kind of a special case though since the validation rules for xsd:anyURI are very permissive. We'll look into improving this for the next release.

 

While I was trying to build sample data to reproduce the problem, the command stopped working altogether. My config file and sample data are attached. Even the exact command which succeed now fails with the same parsing error message.

The config file you sent seems correct and the following commands work fine for me.
Do you have multiple copies of the config file? Are you sure you are using the config file you sent?

Best,

Evre 

 

Here are the commands I used and their output:

$ stardog-admin --server snarl://localhost:myPort db create -n obfDb obfDb.owl
Bulk loading data to new database.
Parsing triples: 100% complete in 00:00:00 (4 triples - 0.4K triples/sec)
Parsing triples finished in 00:00:00.012
Creating index: 100% complete in 00:00:00 (0.8K triples/sec)
Creating index finished in 00:00:00.006
Computing statistics: 100% complete in 00:00:00 (1.3K triples/sec)
Computing statistics finished in 00:00:00.003
Loading complete.
Inserted 4 triples in 00:00:00.113 at 0.0 triples/sec
Bulk load complete.  Loaded 4 triples from 1 file(s) in 00:00:00 @ 0K triples/sec.

Successfully created database 'obfDb'.

$ stardog data obfuscate -c obfConfig.ttl snarl://localhost:myPort/obfDb result.trig
There was an error parsing the obfuscation configuration for the export

Thanks,
Duane

--
-- --
You received this message because you are subscribed to the C&P "Stardog" group.
To post to this group, send email to sta...@clarkparsia.com
To unsubscribe from this group, send email to
stardog+u...@clarkparsia.com
For more options, visit this group at
http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en

[Duane Holt]

On Wednesday, May 21, 2014 10:50:33 PM UTC-4, Evren Sirin wrote:

On Wed, May 21, 2014 at 7:07 PM, Duane Holt <duane....@gmail.com> wrote:

I managed to obfuscate data once, and noticed that the command did not obfuscate xsd:anyURI literals.

That's correct. Right now only string literals are obfuscated and this cannot be changed via the configuration file. The way values are obfuscated right now would create invalid typed literals (e.g. integers would me mapped to arbitrary strings). The xsd:anyURI is kind of a special case though since the validation rules for xsd:anyURI are very permissive. We'll look into improving this for the next release.

 

Okay.  Thanks, Evren!
 

While I was trying to build sample data to reproduce the problem, the command stopped working altogether. My config file and sample data are attached. Even the exact command which succeed now fails with the same parsing error message.

The config file you sent seems correct and the following commands work fine for me.
Do you have multiple copies of the config file? Are you sure you are using the config file you sent?

Yes, its the correct config file.  Not sure what the problem was, but restarting Stardog resolved it.