Re: another question about imports

> --0016e6480624c7ba0d048483c7d9
> Content-Type: text/plain; charset=ISO-8859-1
> 
>  Ok, and how about if in the test document we continue to say, as we
> currently do, that there is one normative version (and the other versions
> are presentation) of an InputDocument, PremiseDocument and
> ImportedDocument?  For an imported RDF document it would be the RDF/XML
> version.

That sounds good.

     - s

> Or do you want to have both the xml and turtle versions normative
> and change the xml schema for the test cases?
> 
> Stella
> 
> 
> On Sun, Apr 18, 2010 at 9:15 AM, Sandro Hawke <sandro@w3.org> wrote:
> 
> > [feel free to quote this in public e-mail]
> >
> > > (I'm not making any changes to the test cases or documentation yet, just
> > > preparing)
> > >
> > > If the location of the imported file is ...import001, how will the
> > > requesting software specify whether it wants the .rdf version or the .ttl
> > > version?
> >
> > We probably need to explain this in the test cases document.
> >
> > When the access is over the web, they do it via an HTTP "Accept" header,
> > using a process known as "Content Negotiation", which shifts the burden
> > of translation between formats over to the server.
> >
> > Specifically, when a client does an HTTP GET operation, there is a
> > parameter in which one may specify the acceptable content types to be
> > returned.   For example:
> >
> >  GET -H 'Accept: application/rdf+xml'
> > http://www.w3.org/ns/entailment/Simple
> >  GET -H 'Accept: text/turtle' http://www.w3.org/ns/entailment/Simple
> >  GET -H 'Accept: text/html' http://www.w3.org/ns/entailment/Simple
> >
> > each one works, and returns different bytes representing what is
> > conceptually the same information in different formats.  With a little
> > configuration, Apache does this automatically if you just provide files
> > with the same base name and different suffixes.
> >
> > I don't think we need to make a big point of this -- any RDF library
> > which can fetch from the web (which is probably all of them) almost
> > certainly has this already implemented.  But yes, we should state this
> > somewhere in the Test Cases document.
> >
> > Also: when running locally, without an HTTP server, there has to be some
> > similar step.  When the URI is turned into a filename, some logic is
> > needed to related the desired format with some filename suffix.
> >
> >     -- Sandro
> >
> 
> --0016e6480624c7ba0d048483c7d9
> Content-Type: text/html; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
> 
> <div>=A0</div>
> <div>
> <div>Ok, and how about if in the test document we continue to say, as we cu=
> rrently do, that there is one normative version (and the other versions are=
>  presentation)=A0of an InputDocument, PremiseDocument and ImportedDocument?=
> =A0=A0For an imported RDF document it=A0would be the RDF/XML version. Or=A0=
> do you want to=A0have both the=A0xml and turtle versions=A0normative and ch=
> ange=A0the xml schema for the test cases?=A0=A0</div>
> 
> <div>=A0</div>
> <div>Stella=A0</div><br><br></div>
> <div class=3D"gmail_quote">On Sun, Apr 18, 2010 at 9:15 AM, Sandro Hawke <s=
> pan dir=3D"ltr">&lt;<a href=3D"mailto:sandro@w3.org">sandro@w3.org</a>&gt;<=
> /span> wrote:<br>
> <blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
> ; PADDING-LEFT: 1ex" class=3D"gmail_quote">[feel free to quote this in publ=
> ic e-mail]<br>
> <div>
> <div></div>
> <div class=3D"h5"><br>&gt; (I&#39;m not making any changes to the test case=
> s or documentation yet, just<br>&gt; preparing)<br>&gt;<br>&gt; If the loca=
> tion of the imported file is ...import001, how will the<br>&gt; requesting =
> software specify whether it wants the .rdf version or the .ttl<br>
> &gt; version?<br><br></div></div>We probably need to explain this in the te=
> st cases document.<br><br>When the access is over the web, they do it via a=
> n HTTP &quot;Accept&quot; header,<br>using a process known as &quot;Content=
>  Negotiation&quot;, which shifts the burden<br>
> of translation between formats over to the server.<br><br>Specifically, whe=
> n a client does an HTTP GET operation, there is a<br>parameter in which one=
>  may specify the acceptable content types to be<br>returned. =A0 For exampl=
> e:<br>
> <br>=A0GET -H &#39;Accept: application/rdf+xml&#39; <a href=3D"http://www.w=
> 3.org/ns/entailment/Simple" target=3D"_blank">http://www.w3.org/ns/entailme=
> nt/Simple</a><br>=A0GET -H &#39;Accept: text/turtle&#39; <a href=3D"http://=
> www.w3.org/ns/entailment/Simple" target=3D"_blank">http://www.w3.org/ns/ent=
> ailment/Simple</a><br>
> =A0GET -H &#39;Accept: text/html&#39; <a href=3D"http://www.w3.org/ns/entai=
> lment/Simple" target=3D"_blank">http://www.w3.org/ns/entailment/Simple</a><=
> br><br>each one works, and returns different bytes representing what is<br>=
> conceptually the same information in different formats. =A0With a little<br=
> >
> configuration, Apache does this automatically if you just provide files<br>=
> with the same base name and different suffixes.<br><br>I don&#39;t think we=
>  need to make a big point of this -- any RDF library<br>which can fetch fro=
> m the web (which is probably all of them) almost<br>
> certainly has this already implemented. =A0But yes, we should state this<br=
> >somewhere in the Test Cases document.<br><br>Also: when running locally, w=
> ithout an HTTP server, there has to be some<br>similar step. =A0When the UR=
> I is turned into a filename, some logic is<br>
> needed to related the desired format with some filename suffix.<br><font co=
> lor=3D"#888888"><br>=A0 =A0 -- Sandro<br></font></blockquote></div><br>
> 
> --0016e6480624c7ba0d048483c7d9--

Received on Sunday, 18 April 2010 14:42:03 UTC