RE: Asset Description Metadata Schema (ADMS) [SEC=UNCLASSIFIED]

I agree with the proposed changes.

Thanks Makx.


> -----Original Message-----
> From: Fadi Maali [mailto:fadi.maali@deri.org]
> Sent: Wednesday, July 31, 2013 2:34 PM
> To: Makx Dekkers
> Cc: Public GLD WG; Phil Archer
> Subject: Re: Asset Description Metadata Schema (ADMS)
> [SEC=UNCLASSIFIED]
> 
> Hi Makx,
> 
> Thanks for the comment and for proposing text for clarifying
> properties descriptions.
> 
> Here is the list of changes I plan to deploy to the document, please
> let me know if you think they are sufficient (I think I can not apply
> them to the Spec now):
> 1. change accessURL description to the text you suggested:
> A landing page, feed, SPARQL endpoint or other type of resource that
> gives access to the distribution of the dataset
> 2. remove "the value is a URL" from the usage note from both
> downloadURL and accessURL
> 3. add "Use accessURL, and not downloadURL, when it is definitely not
> a download or when you are not sure whether it is." to the accessURL
> usage note
> 4. change downloadURL description to the text you proposed:
> A file that contains the distribution of the dataset in a given format
> 
> Best,
> Fadi
> --------------------------------------------------
> Fadi Maali
> PhD student @ DERI
> Irish Research Council Embark Scholarship holder
> http://www.deri.ie/users/fadi-maali
> 
> On 31 Jul 2013, at 13:07, Phil Archer <phila@w3.org> wrote:
> 
> > Just a quick chime in. Text can be clarified after Last Call as long
> as the meaning doesn't change - and this discussion sounds like a call
> for clarity without changing the meaning.
> >
> > Fadi - can I encourage you to log Makx's comment as a Last Call
> comment (which will need a reply and, ideally, a signal from Makx that
> he's happy with that reply).
> >
> > Phil.
> >
> > On 31/07/2013 08:16, Makx Dekkers wrote:
> >>>
> >>> However, regarding defining the range as a literal typed as
> >> xdd:anyURI,
> >>> I don't agree.
> >>> dcat:accessURL is used to refer to a mechanism through which the
> data
> >>> can be accessed. This mechanism can be an API that can be
> represented
> >>> as a rdfs:Resource that needs to be described with further
> properties.
> >>>
> >>
> >> My suggestion was just to align the text with the range of
> >> rdfs:Resource.
> >>
> >> I would be very much against changing the range of the properties
> at
> >> this stage. The DCAT Application Profile that we have just
> finalised
> >> relies on the range of these two properties to be rdfs:Resource.
> >>
> >> Makx.
> >>
> >>
> >>
> >
> > --
> >
> > Phil Archer
> > W3C eGovernment
> >
> > http://philarcher.org
> > +44 (0)7887 767755
> > @philarcher1

Received on Wednesday, 31 July 2013 13:58:01 UTC