Re: PER-s for RDFa 1.1

Good news - I found the right ssh key and was able to sync up.  Since we
need to create local biblio entries for these specs that reference one
another I am planning on using 11 December as the publication date of the
PER unless there is any objection.

On Fri, Nov 28, 2014 at 8:43 AM, Ivan Herman <ivan@w3.org> wrote:

>
> > On 28 Nov 2014, at 15:35 , Shane McCarron <shane@aptest.com> wrote:
> >
> > I have some cycles today - I will see if I remember how to use CVS ;-)
>
> :-)
>
> Ivan
>
> >
> > On Friday, November 28, 2014, Ivan Herman <ivan@w3.org> wrote:
> > Great. I think we can aim at a publication for the 11th of December,
> that is almost two weeks.
> >
> > Manu, as I said, I am happy to make the minor editings that I listed,
> just give me a nod. To be clear, that would mean I can take care of RDFa
> Lite, HTML+RDFa and, of course, the Primer (that one is already done), with
> Shane taking care of Core and XHTML+RDFa (at the minimum all cross
> references should be up-to-date).
> >
> > Ivan
> >
> >
> >
> > > On 28 Nov 2014, at 24:57 , Shane McCarron <shane@aptest.com> wrote:
> > >
> > > I imagine I could find some cycles to do this.  There might also be a
> couple of minor DTD and XML Schema things that need fixing.  Let me check
> my notes.
> > >
> > > On Thursday, November 27, 2014, Ivan Herman <ivan@w3.org> wrote:
> > >
> > > > On 27 Nov 2014, at 11:55 , Ivan Herman <ivan@w3.org> wrote:
> > > >
> > > > Manu, Ralph, Shane,
> > > >
> > > > we have a pending issue that we are now in position to close. Per[1]
> we had to pending issues in HTML+RDFa, waiting for the HTML5
> > >
> > > to -> two :-)
> > >
> > > > and the RDF1.1 recommendations to be published. This is now done.
> This means that we would have re-publish the HTML+RDFa1.1 document with
> following actions:
> > > >
> > > > - remove the note in the Status section of [1]
> > > > - in section 3.1 step 9 the last sentence should be removed;
> @datetime is now normative
> > > > - in section 3.1 step 11 the last sentence should simply say: "This
> feature is non-normative" (Alas!, due to the delay of DOM3, the HTML
> datatype is not normative in RDF1.1 Concepts[2]...)
> > >
> > > Additional, minor things:
> > >
> > > - the reference to HTML5 should be updated to Rec
> > > - The RDF concepts and Turtle references should become normative and
> updated.
> > > - Actually I do not know what the XHTML+RDFa1.1 reference is as an
> informal and referring to the PER an not the Rec; I think that was an
> oversight at the final publication step. Anyway, that should be updated as
> well.
> > >
> > > Ivan
> > >
> > >
> > > >
> > > > This is the minimum that we should do, leading to a PER transition
> request, and a republication of [1] as an (Edited) Recommendation. Once
> that done, the RDFa WG[3] should be formally closed.
> > > >
> > > > However, we should probably do a bit more. The errata document for
> RDFa[4] also contains some minor errors. All of them are, as far as I can
> see, editorial. Caveat: that means we have to republish (as PER-s) not only
> HTML+RDFa, but RDFa Lite, RDFa Core, and XHTML+RDFa. Plus some error in the
> RDFa Primer note. Ie, the whole lot.
> > > >
> > > > I think we should do this asap and close the RDFa 1.1 group. If we
> all agree, we may be able to issue a formal AC review call for the PER
> before Xmas; I guess the work required is pretty insignificant. (There is a
> publication moratorium starting the 19th of December up to the 5th of
> January.) Manu, Shane, if you have problems generating the new versions for
> whatever reasons, I can also do these editings myself.
> > > >
> > > > Ralph, I presume we can handle everything by email, we do not need a
> formal transition call for this; we are talking about PER-s.
> > > >
> > > > Cheers
> > > >
> > > > Ivan
> > > >
> > > >
> > > >
> > > > [1] http://www.w3.org/TR/2013/REC-html-rdfa-20130822/
> > > > [2] http://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/
> > > > [3] http://www.w3.org/2010/02/rdfa/
> > > > [4] http://www.w3.org/2010/02/rdfa/errata.html
> > > >
> > > > ----
> > > > Ivan Herman, W3C
> > > > Digital Publishing Activity Lead
> > > > Home: http://www.w3.org/People/Ivan/
> > > > mobile: +31-641044153
> > > > ORCID ID: http://orcid.org/0000-0003-0782-2704
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > ----
> > > Ivan Herman, W3C
> > > Digital Publishing Activity Lead
> > > Home: http://www.w3.org/People/Ivan/
> > > mobile: +31-641044153
> > > ORCID ID: http://orcid.org/0000-0003-0782-2704
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Shane McCarron
> > > Managing Director, Applied Testing and Technology, Inc.
> > >
> >
> >
> > ----
> > Ivan Herman, W3C
> > Digital Publishing Activity Lead
> > Home: http://www.w3.org/People/Ivan/
> > mobile: +31-641044153
> > ORCID ID: http://orcid.org/0000-0003-0782-2704
> >
> >
> >
> >
> >
> >
> > --
> > Shane McCarron
> > Managing Director, Applied Testing and Technology, Inc.
> >
>
>
> ----
> Ivan Herman, W3C
> Digital Publishing Activity Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> ORCID ID: http://orcid.org/0000-0003-0782-2704
>
>
>
>
>


-- 
Shane McCarron
Managing Director, Applied Testing and Technology, Inc.