blocks|key|1209165|text|我不太确定是否需要这样做，对我来说，缺乏工具意味着缺乏需要。JSON最好作为对象处理(无论如何在JS中都是这样)，并且通常使用对象本身的语言进行转换(Java+for+Java+object从JSON创建，对于Perl、Python、Perl、c#、PHP等也是如此)。只需使用普通赋值(或set、get)、循环等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1209166|我的意思是，XSLT只是另一种语言，需要它的原因之一是XML不是对象表示法，因此编程语言的对象并不完全匹配(层次化xml模型和对象/结构之间的阻力)。|1209167|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Not too sure there is need for this, and to me lack of tools suggests lack of need. JSON is best processed as objects (the way it's done in JS anyway), and you typically use language of the objects itself to do transformations (Java for Java objects created from JSON, same for Perl, Python, Perl, c#, PHP and so on). Just with normal assignments (or set, get), looping and so on.

I mean, XSLT is just another language, and one reason it is needed is that XML is not an object notation and thus objects of programming languages are not exact fits (impedance between hierarchic xml model and objects/structs).

blocks|key|1209296|text|说缺乏工具就意味着缺乏需求，这是在回避问题。这同样适用于Linux中对X或Y的支持(为什么要费心为如此少数的操作系统开发高质量的驱动程序和/或游戏呢？为什么要关注一个大型游戏和硬件公司不为其开发的操作系统呢？)可能需要使用XSLT和JSON的人最终会使用一些琐碎的变通方法:将JSON转换为XML。但这并不是最好的解决方案，不是吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1209297|如果您有一个原生JSON格式，并且希望在浏览器中编辑它"wysywyg“，那么XSLT将是一个非常好的解决方案。用传统的javascript编程做这件事可能会成为一件令人头疼的事情。|1209298|实际上，我已经为XSLT实现了一种“石器时代”的方法，使用子字符串解析来解释javascript的一些基本命令，如调用模板、处理子对象等。当然，使用JSON对象实现转换引擎要比实现完整的XML解析器来解析XSLT容易得多。问题是，要使用XML模板转换JSON对象，需要解析模板的XML。|1209299|要使用XML+(或HTML、文本或其他格式)转换JSON对象，需要仔细考虑语法以及需要使用哪些特殊字符来标识转换命令。否则，您最终将不得不为自己的自定义模板语言设计一个解析器。在经历了这条路之后，我可以告诉你，它并不漂亮。|1209300|更新(2010年11月12日)：在我的解析器上工作了几周后，我已经能够对它进行优化了。模板是预先解析的，命令被存储为JSON对象。转换规则也是JSON对象，而模板代码是HTML和类似于shell代码的自制语法的混合。我已经能够将复杂的JSON文档转换为HTML来制作文档编辑器。编辑器的代码大约有1K行(这是一个私人项目，所以我不能分享它)，JSON转换代码大约有990行(包括迭代命令、简单比较、模板调用、变量保存和求值)。我计划在麻省理工学院的许可下发布它。如果你想参与进来，给我写封邮件。|1209301|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

To say lack of tools suggest lack of need is just begging the question. The same could be applied to support for X or Y in Linux (Why bother developing quality drivers and/or games for such a minority OS? And why pay attention to an OS that big game and hardware companies don't develop for?). Probably the people who would need to use XSLT and JSON end up using a somewhat trivial workaround: Transforming JSON into XML. But that's not the optimal solution, is it?

When you have a native JSON format and you want to edit it "wysywyg" in the browser, XSLT would be a more than adequate solution for the problem. Doing that with traditional javascript programming can become a pain in the arse.

In fact, I have implemented a "stone-age" approach to XSLT, using substring parsing to interpret some basic commands for javascript, like calling a template, process children, etc. Certainly implementing a transformation engine with a JSON object is much easier than implementing a full-fledged XML parser to parse the XSLT. Problem is, that to use XML templates to transform a JSON object you need to parse the XML of the templates.

To tranform a JSON object with XML (or HTML, or text or whatever) you need to think carefully about the syntax and what special characters you need to use to identify the transformation commands. Otherwise you'll end up having to design a parser for your own custom templating language. Having walked through that path, I can tell you that it's not pretty.

Update (Nov 12, 2010): After a couple of weeks working on my parser, I've been able to optimize it. Templates are parsed beforehand and commands are stored as JSON objects. Transformation rules are also JSON objects, while the template code is a mix of HTML and a homebrew syntax similar to shell code. I've been able to transform a complex JSON document into HTML to make a document editor. The code is around 1K lines for the editor (it's for a private project so I can't share it) and around 990 lines for the JSON transformation code (includes iteration commands, simple comparisons, template calling, variable saving and evaluation). I plan to release it under a MIT license. Drop me a mail if you want to get involved.

blocks|key|1209384|text|我最近发现了一个我喜欢的JSON样式工具：https://github.com/twigkit/tempo。非常容易使用的工具--在我看来，使用它比使用XSLT容易得多--不需要XPATH查询。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1209385|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/twigkit/tempo^0|L|W|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I recently found a tool that I love for styling JSON: <a href="https://github.com/twigkit/tempo" rel="nofollow noreferrer">https://github.com/twigkit/tempo</a>. Very easy tool to use--in my opinion, it is much easier to work with than XSLT--no need for XPATH queries.

blocks|key|1424337|text|使用XSLT转换JSON是非常可能的:您需要JSON2SAX反序列化程序和SAX2JSON序列化程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1424338|用Java编写的示例代码：http://www.gerixsoft.com/blog/json/xslt4json|offset|length|1424339|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gerixsoft.com/blog/json/xslt4json^0|0|D|18|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

it is very possible to convert JSON using XSLT: you need JSON2SAX deserializer and SAX2JSON serializer.

Sample code in Java:
<a href="http://www.gerixsoft.com/blog/json/xslt4json" rel="nofollow">http://www.gerixsoft.com/blog/json/xslt4json</a>

blocks|key|1424410|text|我已经厌倦了大量的JavaScript模板引擎，以及它们的内联HTML模板、不同的标记样式等，我决定使用build+a+small+library，它支持对JSON数据结构进行XSLT格式化。这并不是什么高深莫测的科学--它只是将JSON解析成XML，然后用XSLT文档格式化。它也很快，没有Chrome中的JavaScript模板引擎快，但在大多数其他浏览器中，它至少和JS引擎一样快，适用于更大的数据结构。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1424411|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/WelcomWeb/Stapling^0|1G|L|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I've been really tired of the enormous amount of JavaScript templating engines out there, and all their inline HTML-templates, different markup styles, etc., and decided to <a href="https://github.com/WelcomWeb/Stapling" rel="nofollow">build a small library</a> that enables XSLT formatting for JSON data structures. Not rocket science in any way -- it's just JSON parsed to XML and then formatted with a XSLT document. It's fast too, not as fast as JavaScript template engines in Chrome, but in most other browsers it's at least as fast as the JS engine alternative for larger data structures.

blocks|key|1424434|text|为什么不使用Mr.+Data+Coverter将JSON转换为XML，使用XSLT将其转换，然后使用相同的方法将其转换回JSON。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1424435|entityMap|0|LINK|mutability|MUTABLE|url|http://shancarter.com/data_converter/^0|6|H|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Why don't you converts JSON to XML using <a href="http://shancarter.com/data_converter/" rel="nofollow">Mr. Data Coverter</a> , tranform it using XSLT and then change it back to JSON using the same.

blocks|key|1424475|text|试试JOLT。它是一个用Java编写的JSON到JSON转换库。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1424476|之所以特别创建它，是因为我们不想玩“”游戏，并且使用模板进行任何足够复杂的转换都是不可维护的。|1424477|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/bazaarvoice/jolt^0|2|4|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Try <a href="https://github.com/bazaarvoice/jolt">JOLT</a>. It is a JSON to JSON transformation library written in Java. 

It was created specifically because we did not want to play the "JSON -> XML -> XSLT -> XML -> JSON" game, and using a template for any sufficiently complex transform is unmaintainable.

blocks|key|1424540|text|jq+-+lightweight+and+flexible+command-line+JSON+processor|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1424541|它不像XSLT那样是基于模板的，但更简洁。例如，要将name和address字段提取到数组中：[.name,+.address]|style|CODE|1424542|tutorial介绍了一个转换Twitter的JSON+API的示例(+manual有很多示例)。|1424543|entityMap|0|LINK|mutability|MUTABLE|url|http://stedolan.github.io/jq/|1|http://stedolan.github.io/jq/tutorial/|2|http://stedolan.github.io/jq/manual/^0|0|1L|0|0|Q|4|V|7|1B|H|0|0|8|1|10|6|2|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|6|7|Z|8|@$A|10|B|11|F|G]|$A|12|B|13|F|G]|$A|14|B|15|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]|$A|1A|B|1B|1|1C]]|C|$]]|$1|J|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]|T|$5|M|N|O|C|$P|U]]]]

<a href="http://stedolan.github.io/jq/" rel="noreferrer">jq - lightweight and flexible command-line JSON processor</a>

It's not template-based like XSLT, but more concise. e.g. to extract <code>name</code> and <code>address</code> fields into an array: <code>[.name, .address]</code>

The <a href="http://stedolan.github.io/jq/tutorial/" rel="noreferrer">tutorial</a> walks through an example of transforming Twitter's JSON API (and the <a href="http://stedolan.github.io/jq/manual/" rel="noreferrer">manual</a> has many examples).

blocks|key|1424592|text|XSLT支持JSON，如http://www.w3.org/TR/xslt-30/#json所示。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1424593|XML使用尖括号表示分隔符，JSON使用大括号、方括号和...例如，XML较少的标记识别比较意味着它针对声明性转换进行了优化，而更多的比较，就像switch语句一样，出于速度原因，假设了脚本语言中的命令式代码对其有用的推测性分支预测。作为直接结果，对于半结构化数据的不同混合，您可能希望将XSLT和javascript引擎的性能作为响应页面的一部分进行基准测试。对于可以忽略不计的数据有效负载，在没有XML序列化的情况下，转换也同样适用于JSON。W3的决定应该建立在更好的分析基础上。|1424594|entityMap|0|LINK|mutability|MUTABLE|url|http://www.w3.org/TR/xslt-30/#json^0|C|Y|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

XSLT supports JSON as seen at <a href="http://www.w3.org/TR/xslt-30/#json" rel="noreferrer">http://www.w3.org/TR/xslt-30/#json</a>

XML uses angular brackets for delimiter tokens, JSON uses braces, square brackets, ... I. e. XML's fewer token recognition comparisons means it's optimized for declarative transformation, whereas more comparisons, being like switch statement, for speed reasons assume speculative branch prediction that imperative code in scripting languages is useful for. As direct consequence, for different mixes of semi-structured data, you may want to benchmark XSLT and javascript engines' performance as part of responsive pages. For negligible data payload, transformations might work just as well with JSON without XML serialization. W3's decision ought to be based on better analysis.

blocks|key|1424635|text|JSONiq就是这样一种标准，而Zorba是一种开源的C%2B%2B实现。通过将JSONiq添加为原生数据类型，还可以将其视为XQuery。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1424636|entityMap|0|LINK|mutability|MUTABLE|url|http://www.jsoniq.org/|1|http://www.zorba.io/^0|0|6|0|G|5|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

<a href="http://www.jsoniq.org/" rel="nofollow">JSONiq</a> is such a standard and <a href="http://www.zorba.io/" rel="nofollow">Zorba</a> an open-source C++ implementation. JSONiq can also be seen as XQuery with adding JSON as a native data type.

blocks|key|1424719|text|我正在使用Camel+route+umarshal(xmljson)+->+to(xlst)+->+marshal(xmljson)。足够高效(虽然不是100%25完美)，但是很简单，如果你已经在使用Camel的话。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1424720|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I am using Camel route umarshal(xmljson) -> to(xlst) -> marshal(xmljson). Efficient enough (though not 100% perfect), but simple, if you are already using Camel.

blocks|key|1209887|text|有关使用纯JavaScript以及匹配表达式和递归模板背后熟悉的声明性模式的方法的工作涂鸦/概念证明，请参阅https://gist.github.com/brettz9/0e661b3093764f496e36|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1209888|(对于JSON也可以采用类似的方法。)|1209889|请注意，为了方便在JavaScript中表达模板，演示还依赖于Firefox1.8表达式闭包(至少在方法的ES6简写形式可能实现之前是这样)。|1209890|免责声明:这是我自己的代码。|1209891|entityMap|0|LINK|mutability|MUTABLE|url|https://gist.github.com/brettz9/0e661b3093764f496e36^0|1I|1G|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

For a working doodle/proof of concept of an approach to utilize pure JavaScript along with the familiar and declarative pattern behind XSLT's matching expressions and recursive templates, see <a href="https://gist.github.com/brettz9/0e661b3093764f496e36" rel="nofollow">https://gist.github.com/brettz9/0e661b3093764f496e36</a>

(A similar approach might be taken for JSON.)

Note that the demo also relies on JavaScript 1.8 expression closures for convenience in expressing templates in Firefox (at least until the ES6 short form for methods may be implemented).

Disclaimer: This is my own code.

blocks|key|1209895|text|看一看jsonpath-object-transform|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1209896|entityMap|0|LINK|mutability|MUTABLE|url|https://www.npmjs.com/package/jsonpath-object-transform^0|3|P|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Have a look at <a href="https://www.npmjs.com/package/jsonpath-object-transform">jsonpath-object-transform</a>

blocks|key|1209934|text|很久以前，我为我的基于json的json处理框架写了一个dom适配器。它使用nu.xom库。所得到的dom树可以与java+xpath和xslt工具一起工作。我做了一些非常简单的实现选择。例如，根节点总是被称为"+root+"，数组进入具有li个子元素的ol节点(就像在html中一样)，而其他所有东西都只是一个带有原始值的子节点或另一个对象节点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1209935|JsonXmlConverter.java|offset|length|1209936|用法：JsonObject+sampleJson+=+sampleJson();+++++++++org.w3c.dom.Document+domNode+=+JsonXmlConverter.getW3cDocument(sampleJson,+"root");|style|CODE|1209937|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jillesvangurp/jsonj/blob/master/src/main/java/com/github/jsonj/tools/JsonXmlConverter.java^0|0|0|L|0|0|3|3L|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@$D|X|E|Y|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

I wrote a dom adapter for my jackson based json processing framework long time ago. It uses the nu.xom library. The resulting dom tree works with the java xpath and xslt facilities. I made some implementation choices that are pretty straightforward. For example the root node is always called "root", arrays go into an ol node with li sub elements (like in html), and everything else is just a sub node with a primitive value or another object node.

<a href="https://github.com/jillesvangurp/jsonj/blob/master/src/main/java/com/github/jsonj/tools/JsonXmlConverter.java" rel="nofollow noreferrer">JsonXmlConverter.java</a>

Usage:
<code>
JsonObject sampleJson = sampleJson();
 org.w3c.dom.Document domNode = JsonXmlConverter.getW3cDocument(sampleJson, "root");
</code>

blocks|key|1424885|text|Yate+(https://github.com/pasaran/yate)是在XSLT之后专门设计的，具有JPath+(JS的自然XPath等价物)，编译为JavaScript，并具有相当长的生产使用历史。它实际上是没有文档的，但阅读示例和测试应该足够了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1424886|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/pasaran/yate^0|6|V|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Yate (<a href="https://github.com/pasaran/yate" rel="nofollow noreferrer">https://github.com/pasaran/yate</a>) is specifically designed after XSLT, features JPath (a natural XPath equivalent for JS), compiles to JavaScript and has quite a history of production use. It’s practically undocumented, but reading through samples and tests should be enough.

blocks|key|1424933|text|一种尚未给出的方法是使用解析器生成器在XSLT中创建解析器，该解析器解析JSON并生成XML输出。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1424934|在XML会议上经常提到的一个选项是ReX解析器生成器(http://www.bottlecaps.de/rex/)+-尽管该网站上完全没有文档记录，但可以在搜索中找到食谱。|offset|length|1424935|entityMap|0|LINK|mutability|MUTABLE|url|http://www.bottlecaps.de/rex/^0|0|R|T|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

One approach not yet given is to use a parser generator to create a parser in XSLT which parses JSON and produces an XML output.

One option that gets mentioned a lot at the XML conferences is the ReX parser generator (<a href="http://www.bottlecaps.de/rex/" rel="nofollow noreferrer">http://www.bottlecaps.de/rex/</a>) - although totally undocumented on the site, recipes are available on searching.

blocks|key|1425012|text|JSLT非常接近于XSLT的JSON等价物。它是一种转换语言，您可以使用JSON语法编写输出的固定部分，然后插入表达式来计算要插入到模板中的值。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1425013|举个例子：|1425014|{
++"time":+round(parse-time(.published,+"yyyy-MM-dd'T'HH:mm:ssX")+*+1000),
++"device_manufacturer":+.device.manufacturer,
++"device_model":+.device.model,
++"language":+.device.acceptLanguage
}|code-block|syntax|javascript|1425015|它是在Jackson之上用Java实现的。|1425016|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/schibsted/jslt^0|0|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

<a href="https://github.com/schibsted/jslt" rel="nofollow noreferrer">JSLT</a> is very close to a JSON equivalent of XSLT. It's a transform language where you write the fixed part of the output in JSON syntax, then insert expressions to compute the values you want to insert in the template.

An example:

<pre><code>{
 "time": round(parse-time(.published, "yyyy-MM-dd'T'HH:mm:ssX") * 1000),
 "device_manufacturer": .device.manufacturer,
 "device_model": .device.model,
 "language": .device.acceptLanguage
}
</code></pre>

It's implemented in Java on top of Jackson.

Is there an <a href="http://www.w3.org/TR/xslt" rel="noreferrer">XSLT</a> equivalent for JSON? Something to allow me to do transformations on JSON like XSLT does to XML.

XSLT equivalent for JSON

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

有没有与JSON等效的？允许我对JSON进行转换，就像XSLT对XML所做的那样。

问JSON的XSLT等效物
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JSON的XSLT等效物EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问JSON的XSLT等效物
EN