Thanks Sebb,

Indeed I was looking for the complete warning, ie

'https://ofbiz.apache.org,http://ofbiz.apache.org/pmc/ofbiz.rdf'

I did not see that we had already one (right) other asfext:pmc lower:
<asfext:pmc rdf:resource="http://ofbiz.apache.org/pmc/ofbiz.rdf"; />

I just have to remove the commented out one.

This said, despite picking the OFBiz project in the "DOAP Creation" dropdown 
the generated file was containing

<asfext:pmc rdf:resource="https://ofbiz.apache.org"; /> instead of <asfext:pmc 
rdf:resource="http://ofbiz.apache.org/pmc/ofbiz.rdf"; />

Is that normal, is it our task to replace by the right URL? I did not find any 
advice about that.

TIA

Jacques


Le 09/09/2024 à 16:16, sebb a écrit :
On Mon, 9 Sept 2024 at 11:36, Jacques Le Roux
<jacques.le.r...@les7arts.com>  wrote:
Hi,

After creating a new file usinghttps://projects.apache.org/create.html  (DOAP 
Creation),
I merged the changes got in to update our previous doap_OFBiz.rdf
(https://github.com/apache/ofbiz-site/blob/master/doap_OFBiz.rdf)

I add to comment this new merged line (generated by "DOAP Creation")

     <!-- asfext:pmc rdf:resource="https://ofbiz.apache.org";  /-->

because we received this message

     WARN: invalid asfext:pmc 
'https://ofbiz.apache.org,http://ofbiz.apache.org/pmc/ofbiz.rdf' 
inhttps://ofbiz.apache.org/doap_OFBiz.rdf  (URL can't contain control 
characters. 'ofbiz.apache.org, http' (found at least ' '))

I tried to understand the reason but could not. What I'm missing?
It says that the value for asfext:pmc is
'https://ofbiz.apache.org,http://ofbiz.apache.org/pmc/ofbiz.rdf' which
it found in the filehttps://ofbiz.apache.org/doap_OFBiz.rdf

The value must either be the project id (ofbiz) or the URL of a the
PMC RDF for the project; it must not be a list of URLs.

Is it a relation 
withhttps://github.com/apache/ofbiz-site/blob/master/pmc/ofbiz.rdf  ?
The error message does not mention that file.

I noticed that there the indentation for <asfext:pmc rdf:about="ofbiz"> is not 
quite right.

TIA

Jacques

Reply via email to