Fwd: HTTP RFCs as RDF Classes

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Fwd: HTTP RFCs as RDF Classes

Mark Nottingham-2

FYI and of obvious relevance.

Begin forwarded message:

> Resent-From: [hidden email]
> From: Shadi Abou-Zahra <[hidden email]>
> Date: 11 May 2006 7:17:29 AM
> To: [hidden email], [hidden email], [hidden email],  
> [hidden email]
> Cc: [hidden email]
> Subject: HTTP RFCs as RDF Classes
> Organization: World Wide Web Consortium (W3C)
> X-Archived-At: http://www.w3.org/mid/44634779.2020500@...
>
>
> [apologies for cross-posting to relevant lists]
>
> Hi,
>
> For EARL reports, ERT WG needs to provide mechanisms for recording  
> specific Web content that may be negotiated between the server and  
> the client. A URI is therefore not sufficient to identify such  
> content (for example, several versions of a "Web page" under the  
> same URL are being served by language negotiation).
>
> In order to be able to identify such content (aka "resources",  
> "delivery units", "Web unites" etc), ERT WG has translated some of  
> the relevant RFCs into RDF classes and properties. The group has  
> decided to publish this vocabulary as Working Group Notes that are  
> separate from EARL because their scope and usage is really beyond  
> EARL only. We plan to reuse this vocabulary in EARL 1.0 which is  
> currently on Recommendation track.
>
> Since this work may be useful to other groups, we would like to  
> have your feedback and input before publishing these notes. Please  
> provide us ([hidden email]) with any comments by Friday 2nd  
> June, or let me know if you intend to provide comments after this  
> period.
>
> Here are the relevant documents (they are pretty short):
>
> * HTTP in RDF, 8 May 2006, Editors' Note
> <http://www.w3.org/WAI/ER/HTTP/WD-HTTP-in-RDF-20060508>
>
> * RDF822 in RDF, 2 May 2006, Editors' Note
> <http://www.w3.org/WAI/ER/HTTP/WD-RFC822-in-RDF-20060502>
>
> More information about ERT WG work and deliverables:
> <http://www.w3.org/WAI/ER/>
>
>
> Regards,
>  Shadi
>
>
> --
> Shadi Abou-Zahra     Web Accessibility Specialist for Europe |  
> Chair & Staff Contact for the Evaluation and Repair Tools WG |  
> World Wide Web Consortium (W3C)           http://www.w3.org/ | Web  
> Accessibility Initiative (WAI),   http://www.w3.org/WAI/ | WAI-TIES  
> Project,                http://www.w3.org/WAI/TIES/ | Evaluation  
> and Repair Tools WG,    http://www.w3.org/WAI/ER/ | 2004, Route des  
> Lucioles - 06560,  Sophia-Antipolis - France | Voice: +33(0)4 92 38  
> 50 64          Fax: +33(0)4 92 38 78 22 |
>


--
Mark Nottingham     http://www.mnot.net/


Reply | Threaded
Open this post in threaded view
|

Re: HTTP RFCs as RDF Classes

Mark Baker

I took a stab at something like that years ago, but it ends up being
little more than an alternate syntax for HTTP (but hey, if that's what
the QA folks need, great).

As you mentioned on ietf-http-wg, the modelling needs to be done, and
IMO is by *far* the hardest part.

My most recent effort in that direction was the ineptly named, RestRDF;

http://www.markbaker.ca/2002/03/RestRDF/

and it includes pointers to DanC's earlier Larch based work.  It was
also the motivation for RDF Forms.

Mark.

On 5/12/06, Mark Nottingham <[hidden email]> wrote:

>
> FYI and of obvious relevance.
>
> Begin forwarded message:
>
> > Resent-From: [hidden email]
> > From: Shadi Abou-Zahra <[hidden email]>
> > Date: 11 May 2006 7:17:29 AM
> > To: [hidden email], [hidden email], [hidden email],
> > [hidden email]
> > Cc: [hidden email]
> > Subject: HTTP RFCs as RDF Classes
> > Organization: World Wide Web Consortium (W3C)
> > X-Archived-At: http://www.w3.org/mid/44634779.2020500@...
> >
> >
> > [apologies for cross-posting to relevant lists]
> >
> > Hi,
> >
> > For EARL reports, ERT WG needs to provide mechanisms for recording
> > specific Web content that may be negotiated between the server and
> > the client. A URI is therefore not sufficient to identify such
> > content (for example, several versions of a "Web page" under the
> > same URL are being served by language negotiation).
> >
> > In order to be able to identify such content (aka "resources",
> > "delivery units", "Web unites" etc), ERT WG has translated some of
> > the relevant RFCs into RDF classes and properties. The group has
> > decided to publish this vocabulary as Working Group Notes that are
> > separate from EARL because their scope and usage is really beyond
> > EARL only. We plan to reuse this vocabulary in EARL 1.0 which is
> > currently on Recommendation track.
> >
> > Since this work may be useful to other groups, we would like to
> > have your feedback and input before publishing these notes. Please
> > provide us ([hidden email]) with any comments by Friday 2nd
> > June, or let me know if you intend to provide comments after this
> > period.
> >
> > Here are the relevant documents (they are pretty short):
> >
> > * HTTP in RDF, 8 May 2006, Editors' Note
> > <http://www.w3.org/WAI/ER/HTTP/WD-HTTP-in-RDF-20060508>
> >
> > * RDF822 in RDF, 2 May 2006, Editors' Note
> > <http://www.w3.org/WAI/ER/HTTP/WD-RFC822-in-RDF-20060502>
> >
> > More information about ERT WG work and deliverables:
> > <http://www.w3.org/WAI/ER/>
> >
> >
> > Regards,
> >  Shadi
> >
> >
> > --
> > Shadi Abou-Zahra     Web Accessibility Specialist for Europe |
> > Chair & Staff Contact for the Evaluation and Repair Tools WG |
> > World Wide Web Consortium (W3C)           http://www.w3.org/ | Web
> > Accessibility Initiative (WAI),   http://www.w3.org/WAI/ | WAI-TIES
> > Project,                http://www.w3.org/WAI/TIES/ | Evaluation
> > and Repair Tools WG,    http://www.w3.org/WAI/ER/ | 2004, Route des
> > Lucioles - 06560,  Sophia-Antipolis - France | Voice: +33(0)4 92 38
> > 50 64          Fax: +33(0)4 92 38 78 22 |
> >
>
>
> --
> Mark Nottingham     http://www.mnot.net/
>
>
>