Reminder: our telecon this week is Friday, 1500 UTC. Agenda coming
tomorrow, I'm a bit under the weather today.
-Ben
r 12, 2007 7:25 PM
> To: public-rdf-in-xhtml-tf.w3.org
> Subject: Syntax Document Editor's Draft update for review
>
>
> There are still some open issues, but Mark, Steven, and I
> have checked in all of our changes and I have put up a draft
> at http://www.w3.org/Mark
On Wed, 2007-09-12 at 18:24 +0200, Fabien Gandon wrote:
> Hello,
>
> I have just released a new version of:
>
> 1 - the RDFa2RDFXML XSLT transformation:
> http://ns.inria.fr/grddl/rdfa/2007/09/12/RDFa2RDFXML.xsl
>
> 2 - the associated GRDDL profile:
> http://ns.inria.fr/grddl/rdfa/2007/09/
On 9/12/07, Fabien Gandon <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I have just released a new version of:
>
> 1 - the RDFa2RDFXML XSLT transformation:
> http://ns.inria.fr/grddl/rdfa/2007/09/12/RDFa2RDFXML.xsl
>
> 2 - the associated GRDDL profile:
> http://ns.inria.fr/grddl/rdfa/2007/09/12/
There are still some open issues, but Mark, Steven, and I have checked
in all of our changes and I have put up a draft at
http://www.w3.org/MarkUp/2007/ED-rdfa-syntax-20070912/
Please review this document in preparation for the next task force
call. We do not plan on checking in any more
Hello,
I have just released a new version of:
1 - the RDFa2RDFXML XSLT transformation:
http://ns.inria.fr/grddl/rdfa/2007/09/12/RDFa2RDFXML.xsl
2 - the associated GRDDL profile:
http://ns.inria.fr/grddl/rdfa/2007/09/12/
3 - the default RDFa profile now points to this new version
http://ns.in
O.k. I have just implemented it:-) (not yet on the server)
Ivan
Shane McCarron wrote:
> Ivan,
>
> Ivan Herman wrote:
>> Is that true? Ie, do we allow the [..] format for @resource and @about?
>>
> I believe it to be true. @href does not because we are not changing the
> requirements of the u
Ivan,
Ivan Herman wrote:
Is that true? Ie, do we allow the [..] format for @resource and @about?
I believe it to be true. @href does not because we are not changing the
requirements of the underlying language (XHTML 1.1 in this case) .
@resource and @about are new, and permitting URI |
Fabien Gandon wrote:
Shane,
I have a question for my culture: the production 8 says
"Whitespace is defined as in [XML]. On input all whitespace is
preserved - this is exactly as if the value of xml:space, as defined
in [XML], is set to "preserve". If the value of that attribute is set
to "
Shane McCarron a écrit :
In XHTML xml:space is always set to preserve. See
http://www.w3.org/TR/2006/WD-xhtml-modularization-20060705/conformance.html#s_conform_user_agent
production 8
Shane,
I have a question for my culture: the production 8 says
"Whitespace is defined as in [XML]. On inpu
Mark,
Regarding TC29: Fabien and I discussed that on the phone already -
the only thing I was able to do was point to the according resolution [1]
(and tell about the background why I think we did it the way it is now).
IMHO this is not really an RDFa core issue, so I'd propose to
revisit TC29
Mark Birbeck wrote:
>
>
>>
>>
>> bla...
>
> Note that you can do this:
>
>
>
> bla...
>
> @about and @resource support 'safe curie', whilst @href does not.
>
Is that true? Ie, do we allow the [..] format for @resource and @about?
(not implemented in pyRdfa:-(
In XHTML xml:space is always set to preserve. See
http://www.w3.org/TR/2006/WD-xhtml-modularization-20060705/conformance.html#s_conform_user_agent
production 8
Mark Birbeck wrote:
Hi Fabien,
I agree with you...at least I think I do, but I can't find any
suitable references!
I'm almost cer
Hi Ivan,
Excellent...many thanks.
Two small things:
> It seems that Case 3 covers these edge cases, and works. My vote goes
> for that one. The only caveat is, somewhat philosophically, that the
> choice of the subject on the rdf:type triples is not necessarily the
> 'inherited' subject via the
Mark Birbeck wrote:
> Hi Ivan,
>
>> I have not seen any argument (sorry about that...) that would make my
>> opinion change.
>
> With respect, at least you have seen some arguments.
>
> I haven't yet seen anything that convincingly says why we should
> change the parsing rules for CURIEs such
Mark,
(I think that there is one general conclusion of this and similar
discussions we all had in the past: in any setting there are cases which
lead to somewhat awkward RDFa coding.:-( Let alone the fact that what is
awkward and what is not is often a personal opinion... We have to live
with that
Hi Ivan,
> I have not seen any argument (sorry about that...) that would make my
> opinion change.
With respect, at least you have seen some arguments.
I haven't yet seen anything that convincingly says why we should
change the parsing rules for CURIEs such that they are no longer a
super-set o
Hi Fabien,
I agree with you...at least I think I do, but I can't find any
suitable references!
I'm almost certain that leading and trailing white space in element
content in XML is discarded, unless you set @xml:space="preserve".
Now, that does raise an interesting question which we haven't
cons
Mark
(Sigh...)
I keep to my original opinion which was, reworded in your language:
[[[
1. Don't allow it. There is therefore no such thing as a CURIE with no
colon in, and the values of 'next' and 'prev' get converted by a
preprocessor to full CURIEs before processing continues.
]]]
with the ad
Hi Ivan,
Sorry that this is getting complicated. I'll try to explain the issue
a bit better than I have!
First, setting the 'anonymous prefix' to use the 'default namespace'
was not intended to help the OpenID situation. The 'anonymous prefix'
is just the same as in SPARQL where you can define a
Ivan said:
> However... regardless of what the spec says, the reality out
> there is that authos _do_ use @rel/@rev with values that are
> _not_ defined by XHTML. The example of openid or DC are the
> obvious ones. What this also means that the _second_ scheme
> you propose:-) would actually
Hello,
TC29 is the only thing preventing me to release the new transform an
parser and I think it is a pity.
Can anyone explain me how the children nodes of the in TC29
should be processed to pass the test ; in particular the text nodes.
I currently have two options:
1 - I normalize-spac
Mark,
I thought about this again but, I must admit, I did not change my
opinion, even reading through the thread again...
I was actually a bit surprised to read, in Shane's reply[1] that
[[[
XHTML prohibits the introduction of other values that are not namespace
qualified into @rel / @rev (and @
O.k. I understand. Sorry for stirring up the mud...
Ivan
Mark Birbeck wrote:
> Hi Ivan,
>
> As Shane says, this has been discussed many times. The approach we're
> taking is that we'll see how it pans out, but we'll plan for as many
> possibilities as possible.
>
> The CURIEs draft is most defi
24 matches
Mail list logo
