RE: Issue rdf-equivalent-representations

At 02:50 PM 11/15/01 +0000, Jeremy Carroll wrote:
>+ there are a number of adequate fixes with adequate backwardly compatible
>behaviour. Viz -
>    a. mandate that all fragment URIs of a particular URI are in fact bNode's
>and not real URIs e.g. http://www.w3.org/2001/11/rdf/bnode#b1
>
>    b. suggest use of processing instruction
>       e.g. <?rdf-fake-uri http://www.w3.org/2001/11/rdf/bnode?>
>
>    c. use of new attribute rdf:local
>
>
>
>Anyone care to push me over the edge?

I'm not going to push one way or the other;  I understand the attraction of 
fixing this, but I also understand the charter has a purpose.

BUT, if we do decide to fix this, I don't like solution (a) or (b).

However, something like:

    <rdf:Description rdf:local="node"> ...
     :
    <ex:property rdf:local="node" />

seems quite regular and OK.  Also, it suggests, if needed:

    <rdf:Description rdf:local="node" rdf:literal="literalchars"> ...
     :
    <ex:property rdf:local="node">literalchars</ex:property>

#g


------------------------------------------------------------
Graham Klyne                    MIMEsweeper Group
Strategic Research              <http://www.mimesweeper.com>
<Graham.Klyne@MIMEsweeper.com>
       __
      /\ \
     /  \ \
    / /\ \ \
   / / /\ \ \
  / / /__\_\ \
/ / /________\
\/___________/