名前の付け方のガイドライン :
例えば, bookshelf, コレクションボード, ワークデスク, バンブーラックなど.
XML かそれっぽい言語を利用してとにかくテキストファイルに記述する. 多くの場合 3 つぐらい書くと, 自分に本当に必要な正規化された データ構造が見えてくるかな.
本当はちゃんと ERD (Entity-Relationship Diagrams) を描こう.
For example, when a site is coded with semantically meaningful XML, with textual equivalents provided for images and with links named meaningfully, this helps blind users using text-to-speech software or text-to-Braille hardware.
It should be better to conform my pages to the web accessibility proposed by W3C unless it is hard to implement. However I think, on the other hand, things like a game that scrolls its main frame off the window or fairly exciting pages aren't possible to be implemented this way.
When using valid XML document, you need to choose one XML Schema from these :
An XML file basically begins with :
<?xml version="1.0" encoding="UTF-8" ?>
Every tag has to be completed with an ending slash or complemented with the finishing tag.
<li>blah, blah</li>
An XHTML
file
has the <html>
tag with xml:lang
attribute for localization
and must have all lower-cased tags.
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="ja">
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
<script type="text/javascript" src="/hogehoge.js">
</script>
<link rel="stylesheet" type="text/css" href="/default.css" />
<title>Your Home Page</title>
</head>
<body>
........
<p>
Hello. ちんこわ.
</p>
........
</body>
</html>
In XML text,
generally //<![CDATA[
implies that character data
which is not treated as an
XML
element such as scripts
in an XHTML
file begins from this point. On the other hand,
//]]>
ends the character data section.
<script type="text/javascript">
//<![CDATA[
window.onload = function() {
var Period = 100; // in milliseconds
setTimeout("itIntervalTimer(" + Period + ")", Period);
}
//]]>
</script>
In many cases, one or two namespaces should be sufficient
to be specified in a portion like xmlns='some_url'
:
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/">
XHTML (eXtensible HyperText Markup Language) : XHTML 1.1 is the recommended style of HTML pages today as discussed in the previous section.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
XSL (eXtensible Stylesheet Language) : XSL (sometimes called XSLT script) translates XML file into any text files such as HTML or XHTML including CSS and JavaScript inside the language. I have never tried AJAX with this scheme, but maybe it works fine in this way, which enforces the true separation of data and style (style = a set of user-interface rules like formats and scripts) though.
SVG (Scalable Vector Graphics) : SVG is a well-known format for 2D vector graphics by which Encapsulated PostScript (EPS) format is going to be replaced.
MathML : MathML is a low-level specification for describing mathematical expressions as a basis for machine to machine communication. It could be more efficient than the present giant LATEX .
Resource Description Framework & XML (RDF and XML) : RDF forms a conceptual description of web resources expressed with the relationship (predicate) between a subject and an object.
This idea of RDF
is generally utilized in a way combining with
XML
by weblog and news/press sites
and their ads are often displayed as icons like
,
or
.
NewsML , EventsML , SportsML : a framework for push news technology that was formerly spread by Pointcast.com .
VoiceXML : Currently VoiceXML 2.0 specification was finalized.
The VoiceXML specification is discussed here .
XML Parsers :
I don't think it is going to help much in the near future. Because with the current implementation (of Ruby etc.), it is not a direct translation of relatioinal models and thus cannot be recommended for a precise expression of structured data. An object based data structure like a bunch of XML files formulating a knowledge base / unified online manual will get advantage in terms of practical operations over RDBMS in the near future. IMO transaction functions available in RDBMS such as MySQL are only helpful for use in goverment and banks.
Under construction. Have no concrete idea going beyond the idea of term vectors generally used in Amazon and other sites. Any suggestion would be appreciated.
As I mentioned above, ERD (Entity-Relationship Diagram) is the best to choose to describe the relational data models in the first place.
Having said that, maybe you'd like to use an idea like a flow chart that is already old enough and nowadays replaced by UML as well as design patterns.
If you don't like to use XML, you could effectively write in Lisp as a data definition language. That is because, unlike CSV, in the language carriage return does not affect the data structure.
If I'm correct, the most useful things are class charts and domain charts among others. Divide the problem using a domain chart, and conquer it. I guess the class chart can be a representative of XML which is the object relationship in terms of ownership (that owns this).
23 typical object definition patterns suggested by the Gang of Four (GoF).
In the future, automatic generation of design patterns must be realized.
Go to a place that is close to a WLAN spot, then find data that's useful to you or someone, and go back to the Hotspot/BB mobile point for data entry.
Offline data entry - SQL is a candidate but it is very tedious to write with. One way to do it is using XML instead although it requires a dicipline to write in.
Set up webdav, and bring up MySQL, and PHP or possibly Java and Tomcat servlet container with Apache to share information.
Direct Access to this location is not allowedand
Must Enable Legacy Mode In Global Config To Complete This Task.
