@@ -25,6 +25,43 @@ interesting uses for it or have ideas for improvements.
2525
2626See also wiki: https://github.com/rvguha/schemaorg/wiki/Contributing
2727
28+ Formats and standards
29+ =====================
30+
31+ All schemas and examples are in data/ in utf-8 encoded files.
32+
33+ The main schemas file is data/schema.rdfa (utf-8)
34+
35+ While developing schemas, using data/sdo-somethinghere-schema.rdfa can be useful.
36+
37+ The format is based on W3C RDFS in HTML/RDFa format, see http://schema.org/docs/datamodel.html
38+
39+ The examples are stored in data/examples.txt (utf-8)
40+
41+ As with schemas, data/* examples.txt will also be read. It can be useful to develop
42+ using separate files. When vocabulary is finally integrated into the main repository, schema
43+ data will be merged into schema.org. However examples will stay in separate files, as this
44+ works better with git's file comparison machinery.
45+
46+
47+ Github Branch naming
48+ ====================
49+
50+ Since discussion of http://schema.org/Role frequently referred to Ghostbusters,
51+ and we want to name Github branches for upcoming releases without pre-deciding
52+ their final official schema.org version number, we'll start at
53+ http://en.wikipedia.org/wiki/Ghostbusters#Cast and take it from there.
54+
55+ i.e. sdo-venkman, sdo-stantz, sdo-barrett, sdo-spengler, sdo-zeddemore,
56+ sdo-tully, sdo-melnitz, sdo-peck, sdo-lenny, sdo-gozer.
57+
58+ We'll name these 'sdo-venkman', 'sdo-stantz' etc. as this naming pattern is used for
59+ our test builds on Appspot.
60+
61+ See http://schema.org/docs/releases.html for published release history.
62+
63+ The successor to http://schema.org/docs/releases.html#v1.91 is code-named sdo-venkman.
64+
2865Notes
2966=====
3067
0 commit comments