• 1.0ne.org
• Offline Data Stores
• DNS
• Name Space Index
• Historic
  • 0ne.org
  • 0.0ne.org

1.0ne.org

My (Dave Allen Barker Jr) domain.

The File Structure

The directory listings after the domain in the URI. Thoughts on how to organize files within my domain, 1.0ne.org.

Although I love the thought of an all flat sequenced numbering of files (ala Göedel) and describing and organizing them eslewhere via metadata (by RDF?), I don't have to tools in place at this time to make that easy. Therefore, I'll have to compromise somehow for now.

First Level Directory

There will always be a first level directory (<http://1.0ne.org/FLD/>). There is nothing at the root.

Ideally there would be only the root, and all files would live there. Because realistically it is necessary to have content across diverse storage systems or systems of organization, and it is easy to designate partitions by directory, the first level directory will be used.

A redirect from <http://1.0ne.org/> will be provided to an appropriate starting point (<http://1.0ne.org/2/home.html> for now).

(Should I allow directory browsing from the web server? (No, I don't think so, directories are dinosours))

Here's what I've got so far.

0

Ideal space; can only exist when my dream systems are in place. Only "files", no directories. Files are named numbers, no file extensions (filetyping is done via metadata)

1

1^st archive CD (1 Archive).

2

<http://www.xyz.net/~one/>. Like any URL, this will be a HTTP redirect until the content can be consolodated. As of 2006, all content has been moved from xyz and now resides at CSH in the directory xyz.net. A site wide permanent redirect (HTTP 301) from xyz's </~one/> to <http://1.0ne.org/2/> is in place.

3

Java class files. i.e. A RDF Tool class I'm working on can be found at http://1.0ne.org/3/org/_0ne/_1/jena/Tool .

I don't think this is needed and is currently not it use, so don't use it.

4

<http://www.csh.rit.edu/~one/>

5

2^nd archive CD (3 Archive)

6

1.0ne.org's standard traditional style file space.

Don't use it. I'm not sure what I meant.

7

1^st PhotoCD

8

2^nd PhotoCD

9

3^rd PhotoCD

10

URIs, for use in RDF. Not neccessarily defreferencable (but should be someday). Decided to not use URNs after all, so their functionality will be through here.

This space should have it's own index.

11

Webspace on my server (kinda like 6 actually)

12

Drupal

Only refrences from a FLD (First Level Directory) to within the same FLD can be relative, references outside that FLD must be absolute. This allows content within a FLD to function on its own, outside of 1.0ne.org. (May not be important in the future.)

Second Level Directories and Beyond

This is up to the conventions (or lack their of) of the particular FLD.

Other Sub-Domains

More can participate as numbers off 0ne.org, such as 2.0ne.org. Organization within their domain is up to them. See 0ne.org.

DNS

I forget the exact file format for named, but here's the gist of what I'd like. hostIP is the real machine serving the domain.

Offline Data Stores

Basically CDs. Needs a lot of thought, but for now I'll just talk about them.

NameSpace Index

My URNs at <urn:x-1-0ne-org:>. (Updated 2002-10-28)

Decided against the following (2004-11). See <http://1.0ne.org/10>.

Will tack the following minus "/" and making sure the ID part is separated via "#" onto the above URI and convert old references to it.

0/

Experimental, temporary, no collision checking neccessary.

1/

Some undistinguished knowledge, in one place (file, currently defined at </2/2.rdf> to avoid collisions. Easy names.

2/

Image names (see </2/4/image-data.rdf>). A unique number for each.

3/

Vocab used in xml work, not sure of the syntax yet.

4/

Texts (logs) in </2/6/0/log-data.rdf>. Each entity get's it's own ID, which is then used to reference actual HTML files.

5/

Collections (series) in </2/series-data.rdf>?

6/

Extents in </2/4/extents.rdf>. (Image dimensions)

7

Named temporary'ish namespaces, like "7/smallcaps".