47 |
|
|
48 |
- Should we merge spatial into canvas2d? |
- Should we merge spatial into canvas2d? |
49 |
|
|
50 |
RESOLVED: Yes. Can you give me an example where spatial would |
RESOLVED: Yes. Spatial will most likely not |
51 |
be used without canvas2d? The point is, the x and y coordinates |
be used without canvas2d? The point is, the x and y coordinates |
52 |
are pretty specific to canvases, and while I see containment + x + |
are pretty specific to canvases, and while containment + x + |
53 |
y as a reasonable structure orthogonal to everything else, separating |
y is a reasonable structure orthogonal to everything else, |
54 |
containnment and x and y to me does not make sense. |
separating containnment and x and y to does not seem make sense. |
55 |
|
|
56 |
Also, if it's spatial, it should also have z ;) |
Also, if it's spatial, it should also have z ;) |
57 |
|
|
58 |
It would be acceptable to have Spatial be a *superclass* of Canvas2D, |
It would be acceptable to have Spatial be a *superclass* |
59 |
but this might not be worth the trouble. |
of Canvas2D, but this is probably not worth the trouble. |
60 |
|
|
61 |
|
Another point: the x and y are the *default* coordinate |
62 |
|
attributes, see the discussion on extensibility |
63 |
|
(to be done later) in javadoc. |
64 |
|
|
65 |
- What should be the namespace prefix? ``vocabulary``, |
- What should be the namespace prefix? ``vocabulary``, |
66 |
``rdf`` or ``terms`` or ``rdfv``? |
``rdf`` or ``terms`` or ``rdfv``? |
114 |
|
|
115 |
RESOLVED: Not yet. A further PEG will address this issue. |
RESOLVED: Not yet. A further PEG will address this issue. |
116 |
|
|
117 |
|
- Should the URI names contain the .HTML suffix? |
118 |
|
|
119 |
|
RESOLVED: No. It serves zero purpose (except allowing the |
120 |
|
website admin to be lazy) and makes it unintuitive to serve non-HTML |
121 |
|
representations of the namespace (such as RDF Schema). |
122 |
|
|
123 |
|
|
124 |
|
|
125 |
Changes |
Changes |
126 |
======= |
======= |
127 |
|
|
133 |
This means that the code implementing access using the vocab. of a certain |
This means that the code implementing access using the vocab. of a certain |
134 |
class should be relatively independent of the other vocabularies. |
class should be relatively independent of the other vocabularies. |
135 |
|
|
136 |
For instance, a spatial canvas is a reasonable unit: there is a canvas, it contains |
For instance, a spatial canvas is a reasonable unit: there is a canvas, |
137 |
certain nodes at certain locations. However, the PP links (now dLinks) or xu links (now CLinks) |
it contains certain nodes at certain locations. However, the PP links |
138 |
between different canvases do not actually belong in the same place; they are orthogonal |
(now dLinks) or xu links (now CLinks) between different canvases do not |
139 |
to the spatial structure. |
actually belong in the same place; they are orthogonal to the spatial |
140 |
|
structure. |
141 |
|
|
142 |
Currently, our code is pretty well along this structure: CanvasView2D takes |
Currently, our code is pretty well along this structure: CanvasView2D takes |
143 |
care of the spatial canvas, and PPConnector (name needs to change) of the dLinks. |
care of the spatial canvas, and PPConnector (name needs to change) of the dLinks. |
144 |
|
|
145 |
The more independent we can make the codes, the easier it will be to slot in new |
The more independent we can make the codes using the different |
146 |
behaviours. |
orthogonal structural pieces, the easier it will be to |
147 |
|
slot in new behaviours. |
148 |
|
|
149 |
Overall changes |
Overall changes |
150 |
--------------- |
--------------- |
155 |
|
|
156 |
Freeze ``org.fenfire.vocab``. Changes only through PEG process. |
Freeze ``org.fenfire.vocab``. Changes only through PEG process. |
157 |
|
|
158 |
Change the prefix ``http://fenfire.org/vocabulary/`` |
Change the prefix ``http://fenfire.org/vocabulary/`` to |
159 |
to ``http://fenfire.org/rdf-v/``. |
``http://fenfire.org/rdf-v/``. After the prefix, each namespace |
160 |
After the prefix, each namespace shall contain the year and month it was originally |
shall contain the year and month it was originally defined in, |
161 |
defined in, in the form |
in the form ``2003/05/``. After that, the name of the namespace, |
162 |
``2003/05/``. After that, the name of the namespace, lowercase, with .html -suffix. |
lowercase. Finally, the name of the |
163 |
|
resource is specified using ``#`` and the resource name. |
164 |
So, for instance, FF.content would be |
So, for instance, FF.content would be |
165 |
``http://fenfire.org/rdf-v/2003/05/fenfire.html#content``. |
``http://fenfire.org/rdf-v/2003/05/fenfire#content``. |
166 |
|
|
167 |
|
|
168 |
All new words define without PEG go into org.fenfire.vocab.lava |
All new words define without PEG go into org.fenfire.vocab.lava |
171 |
|
|
172 |
All entries in vocabulary classes shall have their **official** |
All entries in vocabulary classes shall have their **official** |
173 |
definitions there, in their javadocs. There shall be no members |
definitions there, in their javadocs. There shall be no members |
174 |
or classes without good documentation. |
or classes without good documentation. This is mandatory for |
175 |
|
offical vocabularies and **strongly** recommended for lava |
176 |
|
vocabularies. |
177 |
|
|
178 |
Vocabulary changes, prior to freezing |
Vocabulary changes, prior to freezing |
179 |
------------------------------------- |
------------------------------------- |
190 |
|
|
191 |
Then, we have left ``xuLinkFrom``, ``xuLinkTo``, ``xuLinkType``. |
Then, we have left ``xuLinkFrom``, ``xuLinkTo``, ``xuLinkType``. |
192 |
We should probably avoid 'xu' in the permanent names, |
We should probably avoid 'xu' in the permanent names, |
193 |
just in case. These should be moved to CLINK.CLink, CLINK.cLinkFrom, |
just in case. These should be moved to CLINK (defined below) |
194 |
|
as CLINK.CLink, CLINK.cLinkFrom, |
195 |
CLINK.cLinkTo for clink, "content link", a term Ted at some point used. |
CLINK.cLinkTo for clink, "content link", a term Ted at some point used. |
196 |
|
|
197 |
FF |
FF |
220 |
/** RDF Vocabulary of content links. |
/** RDF Vocabulary of content links. |
221 |
*/ |
*/ |
222 |
public class FF { |
public class FF { |
223 |
/** The RDF type for content links. An node which is a content link |
/** The RDF class for content links. An node which is a content link |
224 |
* must have both the cLinkFrom and cLinkTo properties. |
* must have both the cLinkFrom and cLinkTo properties. |
225 |
*/ |
*/ |
226 |
static public Object CLink; |
static public Object CLink; |
246 |
/** RDF Vocabulary of 2D spatial canvases. |
/** RDF Vocabulary of 2D spatial canvases. |
247 |
*/ |
*/ |
248 |
public class CANVAS2D { |
public class CANVAS2D { |
249 |
/** The RDF type of spatial 2D canvases. |
/** The RDF class of spatial 2D canvases. |
250 |
* Canvases contain (with the "contains" property |
* Canvases contain (with the "contains" property) |
251 |
* nodes, which shall have the "x" and "y" properties. |
* nodes, which shall have the "x" and "y" properties. |
252 |
*/ |
*/ |
253 |
static public Object Canvas2D; |
static public Object Canvas2D; |
257 |
static public Object contains; |
static public Object contains; |
258 |
/** The x and y coordinates of a node on a canvas. |
/** The x and y coordinates of a node on a canvas. |
259 |
* (node, x, literal), where the literal is parseable |
* (node, x, literal), where the literal is parseable |
260 |
* as a float. |
* as a floating-point number (similar to Java doubles). |
261 |
* Note that these are the <em>default</em> coordinate |
* Note that these are the <em>default</em> coordinate |
262 |
* properties: later on, we might make it possible for a Canvas2D |
* properties: later on, we might make it possible for a Canvas2D |
263 |
* to define its own coordinate attributes, which would take |
* to define its own coordinate attributes, which would take |
269 |
PP |
PP |
270 |
"" |
"" |
271 |
|
|
272 |
Remove everything except association. Move association to DLINK. |
Remove this class. |
273 |
Remove class. PP is really a special-case user interface for a subset of the full |
Move association to DLINK. |
274 |
|
PP is really a special-case user interface for a subset of the full |
275 |
fenfire structure, so it's quite reasonable not to include a special vocabulary for it. |
fenfire structure, so it's quite reasonable not to include a special vocabulary for it. |
276 |
|
|
277 |
DLINK |
DLINK |
301 |
*/ |
*/ |
302 |
public class RDF { |
public class RDF { |
303 |
|
|
304 |
/** The RDF type attribute. A node's type can be declared to be Foo |
/** The RDF type attribute. A node's type can be declared |
305 |
* by a triple * (node, RDF.type, Foo). |
* to be Foo |
306 |
|
* by a triple (node, RDF.type, Foo). |
307 |
*/ |
*/ |
308 |
static public Object type; |
static public Object type; |
309 |
} |
} |