Comments for Articles

Comment on by Mark Joseph

Mark Joseph — Fri, 23 Jan 2026 05:53:21 +0000

Anyone interested in more details about P6R products can leave their questions via our ticketing system at https://support.p6r.com/

Comment on P6R’s PKCS 11 Provider by Mark Joseph

Mark Joseph — Fri, 29 Jan 2021 23:27:09 +0000

No we do not support AIX. We currently support any flavor of Linux, FreeBSD, and Windows. A customer can pay for a port to a platform that P6R does not support.

Comment on p6pythonkmip – a python extension for KMIP by Greg Pepus

Greg Pepus — Mon, 01 Jul 2019 15:36:36 +0000

I Have tried the Python C extensions for KMIP. They work as advertized and I have tried them against Cryptsoft, HyTrust and Safenet KMIP servers. Thanks
Greg

Comment on P6R’s PKCS 11 Provider by Faisal Faruqui

Faisal Faruqui — Thu, 29 Nov 2018 18:33:26 +0000

Is your library supported on AIX?

Comment on XSLT and XPath for JSON by XSLT equivalent for JSON – Knowleage Exchange

XSLT equivalent for JSON – Knowleage Exchange — Mon, 23 Apr 2018 16:59:58 +0000

[…] a company which may have implemented something suitable […]

Comment on XSLT and XPath for JSON by Python:How can I use python finding particular json value by key? – IT Sprite

Fri, 30 Oct 2015 09:48:27 +0000

[…] Maybe this is what you need? p6r.com/articles/2008/05/06/xslt-and-xpath-for-json […]

Comment on Join us at RSA 2014 by Jim Susoy

Jim Susoy — Tue, 25 Mar 2014 00:42:28 +0000

Thanks Gert! It was a lot of work and we had a great time. We met up with lots of current and potential customers and partners. Our primary purpose was to evangelize the OASIS KMIP standard and I think that was a success. It was good see KMIP getting traction and we look forward to helping improve the standard over the coming year.

Comment on P6R KMIP Toolkit Introduction by Detailed differences between KMIP 1.0 and 1.1 | DP企业数据保护加密安全 Andy@SafeNet

Detailed differences between KMIP 1.0 and 1.1 | DP企业数据保护加密安全 Andy@SafeNet — Tue, 04 Mar 2014 15:29:32 +0000

[…] part of the process of modifying our KMIP 1.0 protocol implementation to support the new KMIP 1.1specification we compared the two specifications and listed all of […]

Comment on Join us at RSA 2014 by Gert Mitchell

Gert Mitchell — Wed, 19 Feb 2014 19:40:26 +0000

Jim, Here is wishing you guys lots of Luck and Success, hope everything works out according to plans. Hope you pick up more clients to keep you busy for a long time.

Comment on XSLT and XPath for JSON by Mark Joseph

Mark Joseph — Mon, 03 Oct 2011 21:52:29 +0000

>>I hate to break it to you, but you are wrong about the structure of JSON in general. >>You assume that parse-able JSON is necessarily a document. This is false. JSON represents different types >>of data. >>You further assume that all JSON “documents,” for instance, have a root-level curly-brace-pair. This is >>not necessarily the case. You could, for instance, be representing a naked array with JSON. >>It would use a square-bracket-pair instead. >> Actually we use a document paradigm to simplify things but our parsing and XPATH handles all the cases you mention above. We do not assume that a JSON string starts with a curly brace pair. Our tools also support JsonML completely which is all array based with no problem. (We are referenced on the www.jsonml.com web site.) As a blog document there is limited space to show all the JSON forms we support. >> >>I also find it horrible that all JSON XPath expressions would in general have to lead >>with “/JSON-document/” as that is a ridiculously long string – why not just use “/” as your root string >>and assume the rest? >> I don't much like this either it is a bit too long. XPath requires a root node which JSON does not have to have. This convention makes it easy to tell the XPath processor to handle that case. >> >>And why not support arrays through adding integer offsets as keys? >>For instance: >>[ "a", "b", { "key": 9 }] >>Xpath( “/0″ ) –> “a” >Xpath( “/2/key” ) –> 9 >> I don't believe what you propose is standard XPath. If it is please point me to where in the XPath standard document that you can specify an array index as a path element. >> >> One thing you are missing. Our tools support XSLT and XPATH 2.0 which are significantly more powerful than the 1.0 versions. There still are not many 2.0 implementations out there. Our software allows JSON processing with the power of XPATH 2.0 expressions which include regular expressions. With the full JsonML support it is a powerful tool.