Le 6 déc. 2006 à 11:17, Karl Dubost a écrit :
What Elias is saying is that the effort of RDFa community is
1. compatible with microformats (no changes are asked on this
front)
2. being able to relate information distributed in a document
(people do not want to have necessary to
Ian:
Elias Torres wrote:
On the other hand, we keep missing the point,
that no matter what the syntax is, in microformats
at least (our current answer) we can't differentiate
from class values that are properties/classes(types)
and which ones are not.
Here's at least one good use-case
On Tue, 5 Dec 2006, Elias Torres wrote:
div span class=ibm-part-descriptionour part number span
class=part-id123/span/span/div
Yes? What about it?
I guess this is similar to Karl's example.
div id=order1 class=ibm-order
span class=ibm-part-descriptionour part number
Thanks for your patience trying to work out these extremely hypothetical
examples with me. I need to figure out a way to get the internal
examples out here so we can discuss them concretely. In the meantime,
you have motivated me to look at the existing infrastructure with a
different perspective
I'm back. Sorry for the delay.
Ian Hickson wrote:
On Tue, 5 Dec 2006, Elias Torres wrote:
In one of the products, we need two things: one to specify our own piece
of structure data (call it microformat, call it RDFa data).
Could you give an example of the kind of data you're talking about
On Dec 4, 2006, at 11:04 PM, Elias Torres wrote:
If you can read in the uF wiki [1] there's really not much guidance
on how to parse
one or all of them.
There is more documentation than you suggest. See [1], which
documents how to parse hcards. Much of the hCard parsing guideline
apply
There's plenty of documentation/code/test cases for *specific*
microformats but no general rules for let's say additional fields in an
hCard. Let me know if I'm missing any other documentation or overall
principle in microformats.
-Elias
ryan king wrote:
On Dec 4, 2006, at 11:04 PM, Elias
On Tue, 5 Dec 2006, Elias Torres wrote:
[...]
I'm having trouble understanding what you're doing.
Could you provide some actual code examples? They can be fictional, I'm
just trying to work out what you're doing.
For example:
At the moment we have data defined using by XML schemas that
On Dec 5, 2006, at 2:11 PM, Elias Torres wrote:
There's plenty of documentation/code/test cases for *specific*
microformats but no general rules for let's say additional fields
in an
hCard. Let me know if I'm missing any other documentation or overall
principle in microformats.
You're not
ryan king wrote:
On Dec 5, 2006, at 2:11 PM, Elias Torres wrote:
There's plenty of documentation/code/test cases for *specific*
microformats but no general rules for let's say additional fields in an
hCard. Let me know if I'm missing any other documentation or overall
principle in
On Tue, 5 Dec 2006, Ian Hickson wrote:
p id=order1 class=ibm-order
p
has purchased a
span about=order1 property=ibm-part
The key point here being the reference to an earlier blob in the same
page, right?
Interesting. That's something that currently can
On 12/5/06, Ian Hickson [EMAIL PROTECTED] wrote:
On Tue, 5 Dec 2006, Elias Torres wrote:
p class=ibm-order
span property=ibm-customer
span property=ex-nameIan Hickson/span
(span property=acme-id95237032895/span)
/span
has purchased a
span
On Tue, 5 Dec 2006, Elias Torres wrote:
A few comments on your code. You can handle with n-levels deep, but
not really nested property.
Why not? I don't understand. Could you give concrete examples?
You are also assuming that the content of the element is the entire
value of the
Le 6 déc. 2006 à 11:23, Ian Hickson a écrit :
On Wed, 6 Dec 2006, Karl Dubost wrote:
Interesting. That's something that currently can only really be done
with tables, output, and hyperlinks; I wonder if we should add a
fourth way that is more convenient for Microformat-like data.
And it's
Ian Hickson wrote:
On Tue, 5 Dec 2006, Elias Torres wrote:
Also, remember, we are going after a declarative mechanism that binds
structure to presentation and we don't know ahead of time all of the
properties that are attached to a structure.
I don't see why this is a problem.
I needed a family break. I'm back, sorry for the interruption.
-Elias
Ian Hickson wrote:
On Tue, 5 Dec 2006, Elias Torres wrote:
A few comments on your code. You can handle with n-levels deep, but
not really nested property.
Why not? I don't understand. Could you give concrete examples?
Le 5 déc. 2006 à 05:34, Ian Hickson a écrit :
The other issue, supporting other vocabularies in HTML5, is an open
issue,
but it will be addressed in due course. We need more implementation
experience first, and there are far more pressing problems.
slightly related. What about foreign
Ian Hickson wrote:
On Tue, 5 Dec 2006, Karl Dubost wrote:
Le 5 déc. 2006 à 05:34, Ian Hickson a écrit :
The other issue, supporting other vocabularies in HTML5, is an open
issue, but it will be addressed in due course. We need more
implementation experience first, and there are far more
Le 5 déc. 2006 à 15:09, Ian Hickson a écrit :
On Tue, 5 Dec 2006, Karl Dubost wrote:
Le 5 déc. 2006 à 05:34, Ian Hickson a écrit :
The other issue, supporting other vocabularies in HTML5, is an open
issue, but it will be addressed in due course. We need more
implementation experience first,
Ian Hickson wrote:
On Tue, 5 Dec 2006, Elias Torres wrote:
I work at IBM/Lotus and are in the process of shipping a series of
internal components used by IBM employees as Lotus products. We have
tried using microformats as an extension mechanism for HTML but found
several limitations
On Tue, 5 Dec 2006, Elias Torres wrote:
In one of the products, we need two things: one to specify our own piece
of structure data (call it microformat, call it RDFa data).
Could you give an example of the kind of data you're talking about and how
you'd use it? Obviously I don't mean to ask
21 matches
Mail list logo
