Re: [RIF] ACTION-944: Summarize issue of imports argument and propose a solution from Sandro Hawke on 2009-11-24 (public-rif-wg@w3.org from November 2009)

From: Sandro Hawke <sandro@w3.org>
Date: Tue, 24 Nov 2009 13:58:31 -0500
To: "Boley, Harold" <Harold.Boley@nrc-cnrc.gc.ca>
cc: public-rif-wg@w3.org
Message-ID: <29098.1259089111@waldron>

> ACTION-944 is about the XML syntax of the <Import> type tag
> and possible related classes that RIF dialects may require.
> The <Import> class contains a <location> role tag and an
> optional <profile> role tag.
> 
> Within those <location> and <profile> role tags, we initially
> had <Const> type tags:
> 
> <Document>
>   <directive>
>     <Import>
>        <location>
>          <Const type=3D"&rif;iri">IRI</Const>
>        </location>
>        <profile>
>          <Const type=3D"&rif;iri">IRI</Const>
>        </profile>?
>     </Import>
>   </directive>*
>   <payload>Group</payload>?
> </Document>
> 
> We then noticed that the IRI content here is not a rif:iri
> but an xs:anyURI. So this calls for a class different from
> <Const>, which could be called <Link>, as follows:
> 
> <Document>
>   <directive>
>     <Import>
>        <location>
>          <Link type=3D"&xs;anyURI">IRI</Link>
>        </location>
>        <profile>
>          <Link type=3D"&xs;anyURI">IRI</Link>
>        </profile>?
>     </Import>
>   </directive>*
>   <payload>Group</payload>?
> </Document>

Do you imagine a Link would ever make sense to have somewhere inside a
Condition, in some RIF dialect?  If so, what would it mean?  How would
it be different from a Const?

     -- Sandro

Received on Tuesday, 24 November 2009 18:58:40 UTC