I've updated the Workers specification in response to feedback. The
proposal I sent recently contains a summary of the changes I made:
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2008-August/015853.html
On Sat, 9 Aug 2008, Martin Ellis wrote:
Could it not be set that a there is
Manu Sporny writes:
Ian Hickson wrote:
there are a number of technical merits that speak in favor of RDFa
over Microformats (fully qualified vocabulary terms
Why is this better?
Emulated-namespace/Pseudo-namespace (EN/PN) vocabulary terms have been
mentioned on this list during
Has anyone considered having an URI in an entity in order to avoid typing it
over and over?
e.g.
!DOCTYPE html
!ENTITY myVocab http://www.example.com/vocab/;
And later
Property=myVocab;myPred?
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Actually the chances of name conflict rise square-exponentially, like 1 −
exp(−C*N²)
Chris
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Manu Sporny
Sent: Wednesday, August 27, 2008 4:50 AM
To: Ian Hickson
Cc: WHAT-WG; [EMAIL PROTECTED]
Subject: Re:
Smylers wrote:
...
The other advantage of unique prefixes over URIs is the one you mention:
they are not dereferenceable. As has been mentioned on this list, that
means nobody (human or system) will attempt to reference them, either by
mistake or in the hope of finding something there. This
You cannot support both CURIEs and URLs. What happens when someone declares
xmlns:http?
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Manu Sporny
Sent: Wednesday, August 27, 2008 4:50 AM
To: Ian Hickson
Cc: WHAT-WG; [EMAIL PROTECTED]
Subject:
It is doubtless that semantic networks are a valuable tool in natural
language processing and in reasoning about actions. However, having
semantic networks and plain text as interleaved alternative streams of the
same content, which is what the demonstration shows, seems to be too
vulnerable and
Kristof Zelechovski wrote:
seems to be too vulnerable and error-prone
You're basing this on your impression. The demos that we've been working
on, and the ability with which folks are able to mark up their pages
using FOAF, shows that this isn't all that error-prone at all.
You clearly have a
We have two options for having both human-readable and machine-readable
information in a document: write the structure and generate the text or
write the text and recover the structure. At the very least, if you insist
on having both, there must be a mechanism to verify that they are
consistent.
Kristof Zelechovski wrote:
We have two options for having both human-readable and machine-readable
information in a document: write the structure and generate the text or
write the text and recover the structure. At the very least, if you insist
on having both, there must be a mechanism to
This amounts to saying that URLs take precedence over CURIEs and CURIEs can
be enclosed in brackets in case of any ambiguity. This sounds ridiculous
given the weight you put on avoiding ambiguities and name clashes. Since
the author does not control the URL scheme registration process, he can
Your markup means Kristof is the creator but the text displayed is just
Kristof. It is incomplete; the human reader will not know what it means.
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ben Adida
Sent: Wednesday, August 27, 2008 5:38 PM
To:
Kristof Zelechovski wrote:
This amounts to saying that URLs take precedence over CURIEs and CURIEs can
be enclosed in brackets in case of any ambiguity. This sounds ridiculous
given the weight you put on avoiding ambiguities and name clashes. Since
the author does not control the URL scheme
Kristof Zelechovski wrote:
This amounts to saying that URLs take precedence over CURIEs and CURIEs can
be enclosed in brackets in case of any ambiguity. This sounds ridiculous
given the weight you put on avoiding ambiguities and name clashes. Since
It would.
My recommendation is to require
Kristof Zelechovski wrote:
This amounts to saying that URLs take precedence over CURIEs and CURIEs can
be enclosed in brackets in case of any ambiguity. This sounds ridiculous
given the weight you put on avoiding ambiguities and name clashes. Since
the author does not control the URL scheme
Kristof Zelechovski wrote:
Your markup means Kristof is the creator
of the current page, by default.
but the text displayed is just
Kristof. It is incomplete; the human reader will not know what it means.
Sorry, I should have written:
by h2 property=dc:creatorKristof/h2
-Ben
Kristof Zelechovski wrote:
[...] However, having
semantic networks and plain text as interleaved alternative streams
of the
same content, which is what the demonstration shows, seems to be too
vulnerable and error-prone, especially when there is no validator
at hand
that could verify that
Well, that sounds better. What makes me uneasy is that objects are indeed
taken from the text but predicates are in the attribute values and therefore
they must be duplicated to make a sentence. Perhaps the explanation is that
the objects vary and the predicates are fixed.
Chris
-Original
Hi Smylers,
Thanks for taking the time to read this rather long thread and
contribute to the discussion. Responses to your comments are below. :)
Smylers wrote:
Hi Manu. Do you disagree with the Microformats community's belief about
namespaces being more difficult, or do you think they are
Kristof Zelechovski wrote:
Has anyone considered having an URI in an entity in order to avoid typing it
over and over?
e.g.
!DOCTYPE html
!ENTITY myVocab http://www.example.com/vocab/;
And later
Property=myVocab;myPred?
Yes, we did discuss this at great length in the RDFa community and to
This message is quite related to the whole RDFa discussion going on,
but not to any specific message, so it would be confusing to reply
directly to one of such messages.
First of all, HTML is about structure. I want to make this clear
enough from the beginning because trying to broaden the scope
Manu Sporny wrote:
Kristof Zelechovski wrote:
Has anyone considered having an URI in an entity in order to avoid typing it
over and over?
e.g.
!DOCTYPE html
!ENTITY myVocab http://www.example.com/vocab/;
And later
Property=myVocab;myPred?
Yes, we did discuss this at great length in the RDFa
On 27 Aug 2008, at 17:43, Kristof Zelechovski wrote:
Well, that sounds better. What makes me uneasy is that objects are
indeed
taken from the text but predicates are in the attribute values and
therefore
they must be duplicated to make a sentence.
Well, this works the same way
Kristof Zelechovski wrote:
span about=#jane typeof=foaf:Person property=foaf:name
Jane/span
span about=#jane property=foaf:loves resource=#mac
hates/span
span about=#mac typeof=foaf:Person property=foaf:name
Mac/span .
Ugh. That really hurt.
(I've corrected @instanceof to @typeof in
I encounter sites frequently that want to pop out part of their
application free of the page, into a smaller window. For example,
Pandora radio (http://pandora.com) does this. The player starts out
embedded in the normal content area, but users have the option to pop
it out into a smaller,
Looks like the example code in 1.1.4 Shared workers does
worker.addEventListener rather than worker.port.addEventListener. I
assume this is a bug?
/ Jonas
Kristof Zelechovski wrote:
We have two options for having both human-readable and
machine-readable information in a document: write the structure and
generate the text or write the text and recover the structure. At the
very least, if you insist on having both, there must be a mechanism to
On Thu, Aug 28, 2008 at 9:59 AM, Aaron Boodman [EMAIL PROTECTED] wrote:
I encounter sites frequently that want to pop out part of their
application free of the page, into a smaller window. For example,
Pandora radio (http://pandora.com) does this. The player starts out
embedded in the normal
On Wed, Aug 27, 2008 at 5:23 PM, Robert O'Callahan [EMAIL PROTECTED] wrote:
On Thu, Aug 28, 2008 at 9:59 AM, Aaron Boodman [EMAIL PROTECTED] wrote:
I encounter sites frequently that want to pop out part of their
application free of the page, into a smaller window. For example,
Pandora radio
On Wed, 27 Aug 2008, Aaron Boodman wrote:
Why not just open new window and move the playing audio element from
the old window into the new window? You might need to call play() on
it again in the new window, but you shouldn't lose your place in the
stream.
Hm, that is a good point.
Eduard Pascual wrote:
I would like to encourage this community to learn from what it has
already been done in the past, check what worked, and see why it
worked; then apply it to the problem at hand. If for presentation CSS
worked (and I really think it did; if somebody disagrees I invite you
to
On Thu, Aug 28, 2008 at 12:30 PM, Aaron Boodman [EMAIL PROTECTED] wrote:
Hm, that is a good point. I didn't consider the the audio object would
keep playing smoothly when moved between documents. That seems
unlikely to be reliable across implementations, but I'll keep my
fingers crossed :).
On Wed, Aug 27, 2008 at 6:46 PM, Robert O'Callahan [EMAIL PROTECTED] wrote:
Works on Firefox trunk :-). Testcase attached. (The Vorbis file takes a
while to download so you should probably let it play through once before
trying the test.)
What is the rationale behind having to call play()
Shannon wrote:
I think you were on to something with the CSS-like approach. Ian has
stated earlier that class should be considered a generic categorisation
element rather than only a CSS hook.
Three things:
1) specifying the semantics only in a separate file rules out a very
important use
On Thu, Aug 28, 2008 at 12:27 PM, Ben Adida [EMAIL PROTECTED] wrote:
Shannon wrote:
I think you were on to something with the CSS-like approach. Ian has
stated earlier that class should be considered a generic categorisation
element rather than only a CSS hook.
Three things:
1) specifying
On Thu, Aug 28, 2008 at 2:23 PM, Aaron Boodman [EMAIL PROTECTED] wrote:
On Wed, Aug 27, 2008 at 6:46 PM, Robert O'Callahan [EMAIL PROTECTED]
wrote:
Works on Firefox trunk :-). Testcase attached. (The Vorbis file takes a
while to download so you should probably let it play through once
Silvia Pfeiffer wrote:
1) specifying the semantics only in a separate file rules out a very
important use case: the ability to simply paste a chunk of HTML into
your site and have it carry with it all metadata. Think MySpace, Google
widgets, Creative Commons, This is crucial to the design
On Wed, 27 Aug 2008, Ben Adida wrote:
Consider specifically the Craigslist example, where the user selects a
few of the apartments and says map these.
Clearly, and as the voice-over states, the site needs embedded metadata
that easily connects what the user is pointing to to the
Ben Adida wrote:
Shannon wrote:
I think you were on to something with the CSS-like approach. Ian has
stated earlier that class should be considered a generic categorisation
element rather than only a CSS hook.
Three things:
1) specifying the semantics only in a separate file rules
39 matches
Mail list logo
