[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [camp] YAML parser issues
If we decide to specify the use of YAML for the Deployment Plan, we should require support for YAML 1.1. Right now the nCAMP POC has two parsers, one for the JSON that is used in HTTP requests and responses, and a YAML parser for the DP. The code is slightly more complicated, but only slightly. The YamlBeans JAR file adds 131K to the size of the nCAMP WAR.
name: VitaMinder specifications: - name: VitaMinder WAR type: com.example.java:WAR content: href: VitaMinder.war requirements: - name: Servlet Container Requirement type: comp.example.java:ServletContainer javaVersion: 1.6 servletVersion: 3.0 - name: JDBC Requirement type: com.example.java:JDBCService id: dbService fulfill: "id:vitaminder.sql" - name: VitaMinder SQL id: vitaminder.sql type: com.example.java:SQL content: href: vitaminder.sql requirements: - name: SQL Requirement ref: "id:dbService" ~ gp On 4/25/2013 5:06 PM, Adrian Otto wrote:
YAML 1.1 is fully adequate for achieving the adoption objective. -- Adrian On Apr 25, 2013, at 4:42 PM, "Anish Karmarkar" <Anish.Karmarkar@oracle.com> wrote:+1 We ought to think about 'why' folks want YAML. And the reason is: HumanFriendly(YAML) > HumanFriendly(JSON) If that is true, then the issue of YAML being a JSON superset is of less relevant. No? OTOH, uptake and adoption is important. So if there are very few YAML 1.2 parsers out there then we shouldn't use it. OR if JSON compatibility is important then we should just stick to JSON and move to YAML 1.2 when there are parsers available. -Anish -- On 4/25/13 9:27 AM, GILBERT PILZ wrote:I've been doing some experimenting with YAML parsers and I've discovered that JSON is a subset of YAML 1.2, but not a subset of YAML 1.1. If your parser does not support YAML 1.2, there will be some JSON documents that it cannot parse. The following Java YAML parsers are listed on yaml.org: JyYaml: This looks like a dead project (no commits for over a year). SnakeYaml: SnakeYAML supports YAML 1.1. Issue 166 <https://code.google.com/p/snakeyaml/issues/detail?id=166> in the SnakeYAML project ("Any plan to add support for YAML 1.2 spec ?") says "I do not plan to work on the 1.2 spec (09-jan-2013). Feel free to contribute. Please be aware that 1.2 is not supported by many parsers." YamlBeans: Supports YAML 1.0 and 1.1. If there are any plans to support YAML 1.2, they are not documented. JYaml:Another dead project. Long story short, there is no Java YAML parser (that I can find) that supports YAML 1.2. This means that, for Java implementations of CAMP, you'd have to use a JSON parser for the HTTP requests and responses (e.g. Jackson or GSON) and SnakeYAML for the DP (e.g. SnakeYAML or YamlBeans). This isn't the end of the world, and it may change some time in the future but, for now, we can stop talking about how "JSON is a subset of YAML". Also, if we do use YAML for the DP, we should specify the use of YAML 1.1. ~ gp--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]