[Buildingdata] Re: Catalogues of stuff that's not data

[Christopher Gutteridge]

I'm tempted to suggest we just define oo:CatalogueRecord and oo:inCatalogue


On 03/12/2013 18:31, Alexander Dutton wrote:
> On 03/12/13 14:40, Christopher Gutteridge wrote:
>> First of all, I'll introduce Andrew Milsted who joins my team as a full
>> time equipment.data.ac.uk developer!
> Hello!
>
>> Andrew was looking for a way to specify the corrections to the metadata
>> for a specific item of equipment, rather than the whole catalogue for a
>> university.
> I was looking for a way to do this, too, but haven't found anything. Our
> use case was to model the records about services, so we can expose
> modified and created dates for the records themselves. See
> https://twitter.com/alexsdutton/status/395882586926350337 ff.
>
> (We want to maintain statistics about our service catalogue using the
> data cube vocab, including "how many records have been updated/created
> this month?")
>
>> Does anyone have a good pattern for this before we just busk it?
> You *could* claim a record is a document or a graph, and use
> void:inDataset. Your catalogue would also become a dataset, which I
> don't think is overly wrong.
>
> It's not very explicit though, and I wouldn't mind seeing something better.
>
> Best regards,
>
> Alex
>
>
>
> _______________________________________________
> Buildingdata mailing list
> Buildingdata at ecs.soton.ac.uk
> http://mailman.ecs.soton.ac.uk/mailman/listinfo/buildingdata

-- 
Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg

University of Southampton Open Data Service: http://data.southampton.ac.uk/
You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/buildingdata/attachments/20131203/a8644e9c/attachment.html