Skip to content

Commit dac0093

Browse files
committed
Merge pull request #1 from danbri/master
Syncing from Dan's repository
2 parents e14ee83 + 0871504 commit dac0093

38 files changed

+26282
-12501
lines changed

.gitattributes

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# Set the default behavior, in case people don't have core.autocrlf set.
2+
* text=auto
3+
4+
# Explicitly declare text files you want to always be normalized and converted
5+
# to native line endings on checkout.
6+
*.c text
7+
*.h text
8+
*.rdfa text
9+
*.txt text
10+
*.py text
11+
12+
# Declare files that will always have CRLF line endings on checkout.
13+
*.sln text eol=crlf
14+
15+
# Denote all files that are truly binary and should not be modified.
16+
*.png binary
17+
*.jpg binary
18+

README.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,3 +2,52 @@ schemaorg
22
=========
33

44
Schema.org on app engine
5+
6+
This codebase is a simple Python app used to publish the schema.org site.
7+
8+
It uses Google App Engine, and is designed to allow schema.org contributors to explore
9+
new or improved schemas. The code has a bias towards simplicity and minimal dependencies,
10+
rather than elegance and re-usability.
11+
12+
The app reads its schemas and examples from the data/ directory when it starts up. These
13+
are expressed in simple text formats. Proposals to schema.org can be provided as diffs
14+
or github pull requests.
15+
16+
Internals
17+
=========
18+
19+
Internally, the app uses a simple RDF-like graph data model, and has a parser for
20+
the RDFa Lite subset that we use to represent schemas. Potential contributors are
21+
cautioned that this code is not designed to become a general purpose framework, and
22+
that we're comfortable with it being hardcoded in various ways around the needs and
23+
approaches of schema.org. If that's not too discouraging, do let us know if you find
24+
interesting uses for it or have ideas for improvements.
25+
26+
See also wiki: https://github.com/rvguha/schemaorg/wiki/Contributing
27+
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+
Notes
47+
=====
48+
49+
This documentation concerns the software codebase rather than schema.org itself.
50+
51+
However do note that labels, comments, and documentation should use US English (in the code
52+
and schemas), if a choice between English variants is needed. Please aim for international
53+
English wherever possible.

0 commit comments

Comments
 (0)