Skip to content

Commit 49ce69f

Browse files
committed
Use case for issue #5.
1 parent d028d4e commit 49ce69f

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

UCR/index.html

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,17 @@ <h2>Contributing Use Cases and Requirements</h2>
6565

6666
<section>
6767
<h2>Submitted Use Cases</h2>
68-
68+
69+
<section>
70+
<h4>Compatibility with existing libraries</h4>
71+
<p><a href="https://github.com/json-ld/yaml-ld/issues/5">Submitted Use Case</a></p>
72+
<p>
73+
As a developer of YAML-LD processors. I want to be able to use off-the-shelf libraries for converting between JSON-LD and YAML-LD serialization formats. So that data produced in JSON-LD can be easily represented in YAML-LD and visa-versa.
74+
</p>
75+
<p class="note">
76+
There seems to be general compatibility between YAML libraries that produce equivalent results when serializing data originally parsed from JSON. This should be verified, but indicates an easy way of providing a YAML-LD serialization fully round-trippable with JSON-LD.
77+
</p>
78+
</section>
6979
</section>
7080
</body>
7181
</html>

0 commit comments

Comments
 (0)