Fw: RDDL: Should xlink:arcrole or xlink:role be the primary way todispatch on related resources? was Re: URIs, names and well known RDDL names,

[Jonathan Borden <jborden@mediaone.net>]

Ron Daniel asked me to forward this response to the group ... -Jonathan


> Jonathan Borden said:
> 
> 
> >     Note that the argument I present below is dependent on my 
> > reading of Ron
> > Daniel's xlink2rdf w3c note: http://www.w3.org/tr/xlink2rdf 
> > ... i've cc'd
> > Ron and Eve Maler, to give them the opportunity to clarify or 
> > correct my
> > analysis, and as I've said before, I can see both sides of 
> > the argument, so
> > if after the arguments are presented and discussed, the group 
> > decides one
> > way, I will agree.
> > 
> 
> Apologies for not being up to speed on RDDL. My laptop
> was confiscated over the holidays by the IT department
> so they could update it in light of our acquisition by
> Interwoven, our new move to larger facilities, etc.
> Faced with the prospect of reading thousands of xml-dev
> emails, I deleted the lot and am starting again from
> scratch.
> 
> I can speak to some of the RDF related points Jonathan
> mentions, but will then have to ask some questions about
> the intent of RDDL that I did not see in the draft NOTE
> Jonathan cited.
> 
> Jonathan's explanation of the mapping of xlink:arcrole
> and xlink:role to RDF is essentially correct. If you have
> two 'documents', XLink lets you specify BOTH the type of
> relation between the two documents and the role of the
> destination document. An example from a different area
> may illustrate. Assume we have a large document composed
> of parts. The whole document has the identifier 'A', the
> others have identifiers 'B', 'C', ... We could define an
> arcrole between A and B like 'has-part'. We could define
> a role for 'B' like 'Preface' or 'FrontMatter'.
> The mapping NOTE gives a way to express both of those in
> RDF models in a way that is consistent (IMHO) with RDF's
> view of the world.
> 
> One thing I don't know is what you are referring to by the
> distinction between 'primary' and 'secondary'.  What is
> the difference and why is it important?
> 
> Also, a brief step onto the soapbox before closing... Just
> because XLink provides both arcrole and role does not mean
> you have to use them both. First, figure out the problem you
> are solving. Then figure out the tools you need to use.
> (My apologies, naturally, if you have figured out all that
> stuff and I had deleted it.)
> 
> It is tempting to try and classify documents by their 'type',
> only to discover later that you are mixing different notions
> of type. Another example from another area - a file that
> contains an image for a magazine has several notions of type:
>    format: image/gif
>    genre:  election results
>    presentation: map
>    audience: advanced
>    ...
> 
> Is there a list of the sorts of documents you want to associate
> with the namespace URI, and the sorts of things you want to
> do with those documents?
> 
> Regards,
> 
> (NOTE - New contact info effective 01/01/01)
> Ron Daniel Jr.
> Interwoven, Inc.
> 101 Second Street, 4'th floor
> San Francisco, CA 94105
> +1 415 778 3113
> rdaniel@interwoven.com 
> 
>