Okay, that was what I thought. I guess for the W3C note it makes sense to
have a strong rule set.
Alasdair, will the validator highlight properties that should be removed in
order to fit a certain profile? Not sure how easy/hard it would be to
implement though.
Joachim
On 28 November 2013 13:53
The reason for this is that we want to distinguish each of these forms, and
allowing users to add any of these special attributes would undermine and
confuse the process.
m.
On Tue, Nov 26, 2013 at 1:42 PM, Joachim Baran wrote:
> Hello,
>
> On 26 November 2013 09:33, Gray, Alasdair J G wrote:
Hello,
On 26 November 2013 09:33, Gray, Alasdair J G wrote:
> [...] I have also used NEVER to indicate when a property should not be
> associated with a description profile.
>
NEVER seems quite a strong indication. For example, if I have a catalog
description and additionally include dct:creat
Alasdair,
yes, this is exactly right.
m
> On Nov 26, 2013, at 6:33 AM, "Gray, Alasdair J G" wrote:
>
> Hi
>
> I have created the properties table. For ease of editing, I have created this
> in a separate spreadsheet which we can then incorporate into th
Hi
I have created the properties table. For ease of editing, I have created this
in a separate spreadsheet which we can then incorporate into the final version.
There is currently a placeholder link.
https://docs.google.com/spreadsheet/ccc?key=0AvXLyU5sa2XWdGZZRy11ZjhFREZBdndwUVptQ094eWc&
excellent! looking forward to it
m.
On Mon, Nov 25, 2013 at 9:29 AM, Gray, Alasdair J G wrote:
> Hi
>
> I think I've got a good handle now on how to present the properties in a
> table with their types.
>
> I'm on the bus home currently so likely to be tomorrow before I can start
> putting th
Hi
I think I've got a good handle now on how to present the properties in a table
with their types.
I'm on the bus home currently so likely to be tomorrow before I can start
putting them in.
Alasdair
Alasdair J G Gray
Lecturer in Computer Science, Heriot-Watt University, Edinburgh, UK.
Email:
