Oxygen frameworks directory structure…?
Posted: Sat Mar 05, 2011 7:43 pm
I’ve been trying to develop more customized defaults for Oxygen, and I decided to mirror Oxygen’s frameworks directory structure in a separate location (and then customize-as-I-go until I arrive at something stable).
So I looked around in Oxygen’s frameworks directory, and I’m noticing that some directories inside /frameworks seem to have a common structure, while others do not.
For example, some directories have various types of schemas (and DTDs) organized by type (that is, DTDs live under /dtd , RNGs live under /rng , and so on). However, other frameworks have schemas in their top level (such as /frameworks/xml, which contains DTDs and XSDs…and /frameworks/xforms, which contains a catalog.xml and a bunch of XSDs).
Is there an underlying logic behind the structure of these frameworks? Or are these difference simply the result of developer preferences changing over time (or perhaps between developer teams working on different frameworks)?
So I looked around in Oxygen’s frameworks directory, and I’m noticing that some directories inside /frameworks seem to have a common structure, while others do not.
For example, some directories have various types of schemas (and DTDs) organized by type (that is, DTDs live under /dtd , RNGs live under /rng , and so on). However, other frameworks have schemas in their top level (such as /frameworks/xml, which contains DTDs and XSDs…and /frameworks/xforms, which contains a catalog.xml and a bunch of XSDs).
Is there an underlying logic behind the structure of these frameworks? Or are these difference simply the result of developer preferences changing over time (or perhaps between developer teams working on different frameworks)?