[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti-users] Re: Announcing python-stix2
Greg, all,
I have followed the STIX development over the past couple of years, and
even developed a Java library for STIX manipulation, see https://github.com/uw-dims/stix-java.
That was when STIX 1.1 was current.
I watched with some dismay as the XML schema way of doing things in STIX
1.1 was dismantled in favor of JSON for STIX 2. While XML schemas
are complicated, they are very precise, and a document can be checked against
a schema to assert its validity. Further, the richness of tools for
XML schemas, notably the JAXB/xjc tools for Java, gives developers a huge
leg-up in implementing an API for STIX manipulation. I just cranked
the JAXB handle over the .xsd file set, and hey presto I had a set of Java
classes with which to start my API.
Going out on a limb here, I also think that Java developers LIKE more discipline
that Python developers. Static typing vs duck typing? The XML
schema way of representing information is disciplined, and leads to fewer
'You meant X? I thought you meant Y' gotchas at runtime. Extrapolating,
I think the JSON way of data representation is less disciplined than the
XML way, hence the natural inclination of Python developers to prefer JSON.
Looking at the STIX 2 specs, I admire effort the authors must have put
in. But from a library builder's point of view, there being no machine-ingestable
docs (ie the xsd files in STIX 1.1), I am back to square one (if I have
missed any machine-readable docs, I apologize).
So, in a nutshell, my own feeling is that there will be no Java-language
STIX 2 manipulation tools, a sad fact, and I sincerely hope I am wrong
in this respect. I do know that I won't add to my STIX 1.1 Java effort.
Stuart
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]