W3C home > Mailing lists > Public > public-data-shapes-wg@w3.org > March 2015

Re: Question of organization of Requirements wiki page

From: Holger Knublauch <holger@topquadrant.com>
Date: Fri, 06 Mar 2015 08:04:42 +1000
Message-ID: <54F8D2FA.3000101@topquadrant.com>
To: public-data-shapes-wg@w3.org

On 3/6/15 6:56 AM, Richard Cyganiak wrote:
> Two questions on the organization of the Requirements wiki page.
>
> First, there is a section 2.6, “Complex Constraints”.
> https://www.w3.org/2014/data-shapes/wiki/Requirements#Complex_Constraints
>
> This section contains 11 constraints.
>
> Some of them don’t seem particularly complex to me.
>
> What does the title of the section mean? Should I not read to much into it, and simply see it as a bag of functionality that is supposed to be covered by the higher-level constructs?

I think I started this separation, to clarify which parts have to be 
covered by high-level built-in templates, and which features may be left 
to SPARQL. The name "Complex" is misleading and I welcome suggestions.  
As with any "complex" query, anyone could write new high-level term such 
as templates and functions themselves.

Holger

>
> Second, where there any decisions made yet about constructs that will go into the higher-level language, or constructs that will not go into the higher-level language?
>
> If so, how can I see and identify those decisions in the Requirements wiki page?
>
> (If not, maybe someone with strong opinions about the higher-level language could draft a strawman list of *uncontroversial* constructs that should be in there, for bulk approval in a future call?)
>
> Thanks,
> Richard
Received on Thursday, 5 March 2015 22:05:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:30:17 UTC