What's the use case? More generally, in WD3 at least, there are no examples of alternateOf or specializationOf in use (with or without attributes).
If we want to make things really uniform, we could identify a common "template" for all of the record forms
record(id, blah, blah, ... , attrs)
Most of the rules in ProvRDF have this form already.
--James
On Feb 14, 2012, at 9:33 AM, Luc Moreau wrote:
> Hi James,
>
> I think it was an oversight on our behalf (Paolo and I) not to include
> an id for alternateOf/specializationOf. In our working copy,
> http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/towards-wd4.html
> we have added them.
>
> I also take the view that if we have an id then we have attributes, and vice-versa.
>
> As a minimum, subtyping would be useful for these relations.
> You will also recall, very early discussions about mapping of attributes for IVPof.
> This could also be encoded with attributes.
>
> Cheers,
> Luc
>
>
> On 02/14/2012 09:18 AM, James Cheney wrote:
>> While we're on the subject, I'm no sure why alternateOf and specializationOf have attributes now, other than uniformity.
>>
>> I think that if the relation has an id describing the relationship (used/Usage, rtc.) Then attributes make sense. If an id doesn't make sense then attributes don't either - in RDF we need an id to hang the attributess off of.
>>
>> I think that brevity should take precedence over uniformity, else we'll reinvent RDF or XML.
>>
>> --James
>>
>>
>>
>
> --
> Professor Luc Moreau
> Electronics and Computer Science tel: +44 23 8059 4487
> University of Southampton fax: +44 23 8059 2865
> Southampton SO17 1BJ email: l.moreau@ecs.soton.ac.uk
> United Kingdom http://www.ecs.soton.ac.uk/~lavm
>
>
>
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.