Re: strange terms defined by reference in RDF Semantics

On 4/4/23 17:17, Gregg Kellogg wrote:
>> On Apr 4, 2023, at 2:13 PM, Peter F. Patel-Schneider 
>> <pfpschneider@gmail.com> wrote:
>>
>>
>>
>> On 4/4/23 17:09, Gregg Kellogg wrote:
>>>> On Apr 4, 2023, at 1:40 PM, Peter F. Patel-Schneider 
>>>> <pfpschneider@gmail.com> wrote:
>>>>
>>>> RDF Semantics has citations of RDF Schema and SPARQL Entailment Regimes.
>>>>
>>>> In H.2 Terms defined by reference there ends up
>>>>
>>>> [ RDF12-SCHEMA ] defines the following:
>>>>
>>>>    RDF 1.2 Schema
>>>>
>>>> [ SPARQL12-ENTAILMENT ] defines the following:
>>>>
>>>>    SPARQL 1.2 Entailment Regimes
>>>>
>>>> This looks like a bug.  How can I get rid of the terms?
>>> If you click on the link in the “Terms defined by reference” section, it 
>>> should take give you a link to each place that term is used. For RDF 1.2 
>>> Schema, it is used in the Abstract, Set of Documents, and Informative 
>>> references sections. As every documnent in our set if iin the Set of 
>>> Documents section, they will all show as informative references.
>>> Gregg
>>
>>
>> But how do I keep the citations and get rid of these extraneous terms?
> 
> The terms are directly related to the citations, as I mentioned elsewhere. I 
> don’t believe there’s any way to cite documents without ReSpec creating 
> something like a term.
> 
> Note that the two sections in the Index: “Terms defined by this specification” 
> and “Terms defined by reference” could be considered more of an editing aid, 
> and we may decide to not keep them long term; but, they are useful to see what 
> terms are being defined or used. Personally, I find this useful and don’t 
> think it’s a problem.
> 
> Gregg
> 
>> peter
> 


Looking at Section H.2 in RDF Semantics over half of the terms there are not 
terms at all.   The entries are at best worthless and much more likely 
misleading.

There needs to be a way of referring to other specifications that does not 
generate a term.   If there isn't the working group should just not use ReSpec 
(or whatever is generating this bad information).

peter

Received on Tuesday, 4 April 2023 21:36:33 UTC