I have put online a document that describes my idea/proposal for a
selector-based solution to metadata.
The document can be found at http://herenvardo.googlepages.com/CRDF.pdf
Feel free to copy and/or link the file wherever you deem appropriate.
Needless to say, feedback and constructive criticism
On Thu, May 14, 2009 at 9:50 AM, Eduard Pascual wrote:
> I have put online a document that describes my idea/proposal for a
> selector-based solution to metadata.
> The document can be found at http://herenvardo.googlepages.com/CRDF.pdf
> Feel free to copy and/or link the file wherever you deem ap
In part 0.1 you include some HTML and some RDF triples that you'd
like to mark up in the HTML and conclude that RDFa is incapable of
doing that without adding extra wrapper elements.
While adding redundant wrapper elements and empty elements is
occasionally needed in RDFa (and from what I c
(Could you try to be a little more careful about changing mail titles?
These threads have splintered into half a dozen separate things in my
mail reader due to "Re:"s appearing in subjects. It took me a while
to discover just what mail you were trying to respond to here.)
On Sat, May 16, 2009 at
First of all, thanks for the time taken to review the document and to
post your feedback. I truly appreciate it.
On Sat, May 16, 2009 at 2:12 PM, Toby A Inkster wrote:
> In part 0.1 you include some HTML and some RDF triples that you'd like to
> mark up in the HTML and conclude that RDFa is incap
Note: I wrote this yesterday. My internet connection wasn't working as
desirable, but GMail told me it had been sent and I believed it. Now I
have just noticed that it hadn't; and at least one person has been
confused by the changes in the document. Sorry for this issue, and
hope this time GMail do
Given that one of the objections people cite with RDFa is complexity,
I'm not sure how this resolves things. It seems twice as complicated to
me. It creates fewer new attributes, true, but number of attributes
themselves don't create much confusion.
e.g. which is a simpler syntax:
http://foo.exam
On Wed, May 20, 2009 at 11:56 AM, Toby Inkster wrote:
> Given that one of the objections people cite with RDFa is complexity,
> I'm not sure how this resolves things. It seems twice as complicated to
> me. It creates fewer new attributes, true, but number of attributes
> themselves don't create mu
On 20 May 2009, at 23:10, Tab Atkins Jr. wrote:
Stuffing multiple discrete pieces of information makes things
harder for
parsing, harder for authoring tools and harder for authors. In RDFa,
each attribute performs a simple role - e.g. @rel specifies the
relationship between two resources; @rev
On Wed, May 20, 2009 at 6:56 PM, Toby Inkster wrote:
> Given that one of the objections people cite with RDFa is complexity,
> I'm not sure how this resolves things. It seems twice as complicated to
> me. It creates fewer new attributes, true, but number of attributes
> themselves don't create muc
On Thu, 2009-05-21 at 13:26 +0200, Eduard Pascual wrote:
> [... lots ...]
Eduard, thanks for your long and informative reply. I won't go into
every point mentioned in detail, but in summary I'd like to say that
your message reassured me on a few points and perhaps CRDF is not as bad
as I initiall
On Thu, May 21, 2009 at 5:19 PM, Toby Inkster wrote:
> On Thu, 2009-05-21 at 13:26 +0200, Eduard Pascual wrote:
> [... lots ...]
I won't go point by point through your reply neither, but there are
some points worth answering.
> CSS was invented as a way to separate out content from styling. Or to
On Fri, 2009-05-22 at 12:26 +0200, Eduard Pascual wrote:
> Are you calling the DOM Consistency Principle a "theoretical" or
> "aesthetic" argument?
Certainly not -- DOM consistency is a great idea. But given that the
HTML5 spec defines how the DOM is built, there's a very simple solution
to that -
On May 22, 2009, at 17:44, Toby Inkster wrote:
But given that the
HTML5 spec defines how the DOM is built, there's a very simple
solution
to that -- HTML5 could simply mandate that:
http://foo.example.com/";>
generates an identical DOM representation in both XHTML5 and HTML5.
What's
On Fri, May 22, 2009 at 5:26 AM, Eduard Pascual wrote:
> On Thu, May 21, 2009 at 5:19 PM, Toby Inkster wrote:
>> [... some stuff about how will English change in a thousand years ...]
>>
>> A great help in clarifying your usage of terms is the inclusion of a
>> glossary. For example, I could writ
On Thu, 14 May 2009, Eduard Pascual wrote:
>
> I have put online a document that describes my idea/proposal for a
> selector-based solution to metadata. The document can be found at
> http://herenvardo.googlepages.com/CRDF.pdf Feel free to copy and/or link
> the file wherever you deem appropriat
First of all, Ian, thank for your reply. I appreciate any opinions on
this subject.
On Wed, Jun 10, 2009 at 1:29 AM, Ian Hickson wrote:
> This proposal is very similar to RDF EASE.
Indeed, they are both CSS-based, and they fulfill similar purposes.
Let me, however, highlight some differences:
1st,
On Wed, 10 Jun 2009, Eduard Pascual wrote:
> >
> > I think this is a level of indirection too far -- when something is a
> > heading, it should _be_ a heading, it shouldn't be labeled opaquely
> > with a transformation sheet elsewhere defining that is maps to the
> > heading semantic.
>
> That d
On Thu, Jul 9, 2009 at 12:06 AM, Ian Hickson wrote:
> On Wed, 10 Jun 2009, Eduard Pascual wrote:
>> >
>> > I think this is a level of indirection too far -- when something is a
>> > heading, it should _be_ a heading, it shouldn't be labeled opaquely
>> > with a transformation sheet elsewhere defini
I have put a new version of the CRDF document up [1]. Here is a
summary of the most significant changes:
* Location: with the migration from "Google Pages" to "Google Sites",
the PDF document will not be allowed anymore to be hosted at its
former location. I wanted to keep this proposal independen
20 matches
Mail list logo