- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Mon, 28 May 2018 18:02:53 +0200
- To: Franck Michel <franck.michel@cnrs.fr>, public-earl10-comments@w3.org
Dear Franck, Indeed, this document models the HTTP vocabulary, mainly as specified in RFC 2616 and 4229. It does not model the individual parts of the URL/URI vocabulary as per RFC 2396 and 3986. You can only specify the URL/URI as a Literal through the requestURI property: - https://www.w3.org/TR/HTTP-in-RDF10/#requestURIProperty At the time of creating this document the responsible working group did not have the need for breaking down URL/URIs any further than a Literal. The Literal would need to be parsed to extract the query parameters. The responsible working group is no longer active, but I would be interested if you develop a complementary vocabulary for URL/URIs. Regards, Shadi On 25/05/2018 10:26, Franck Michel wrote: > Dear list, > > I'm considering the HTTP Vocabulary for some use case. The vocabulary > provides a means to describe all sorts of HTTP request and response > headers, however I fail to see how to describe parameters passed on the > query string, e.g. param1 and param2 in: > http://path?param1=value¶m2=value2. > > Am I missing something or is this not addressed? I would appreciate if > someone could explain the motivation of this choice, and possibly point > me to some other vocabulary allowing to describe such query string > parameters. > > Best regards, > Franck. > > -- > signature > > Franck MICHEL > CNRS research engineer > +33 (0)4 8915 4277 > franck.michel@cnrs.fr <mailto:franck.michel@cnrs.fr> > > > > Université Côte d’Azur, CNRS- I3S - UMR 7271 > 930 route des Colles - Bât. Les Templiers > BP 145 - 06903 Sophia Antipolis CEDEX - France > Tel. +33 (0)4 9294 2680 > -- Shadi Abou-Zahra - http://www.w3.org/People/shadi/ Accessibility Strategy and Technology Specialist Web Accessibility Initiative (WAI) World Wide Web Consortium (W3C)
Received on Monday, 28 May 2018 16:03:26 UTC