www-site-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergio Fernández <wik...@apache.org>
Subject Re: DOAP format question
Date Mon, 04 May 2015 19:50:08 GMT
On Mon, May 4, 2015 at 9:04 PM, sebb <sebbaz@gmail.com> wrote:

> > The term must be used exactly in the same way it is defined by the
> > namespace/vocabulary/ontology, otherwise won't be processed as expected.
> Theoretically, but not in this case.
> The processing is defined by XSL files that were manually created.
> So whatever the files are coded to expect is what will work.
> This may or may not be the same as the definition.
> In fact at present the XSL files have been coded to accept both
> asfext:PMC and asfext:pmc.
> Only one of these can be correct in terms of the formal definition.

OK, but that's because whoever code the XSLT decided to be defensive to
such interpretation. But that does not mean is right.

> The problem is that it is not clear what the formal definition is.

No, the formal definition is clear at the ns file:

> It would help to know what the formal definition of the asfext
> namespace actually means.

Ok, let's try to put it eas. This is the definition from the namespace (rdf

<rdf:Property rdf:about="http://projects.apache.org/ns/asfext#pmc">
  <rdfs:isDefinedBy rdf:resource="http://projects.apache.org/ns/asfext#" />
  <rdfs:label xml:lang="en">PMC</rdfs:label>
  <rdfs:comment xml:lang="en">ASF Project Management
  <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal" />
  <rdfs:subPropertyOf rdf:resource="
http://www.w3.org/2000/01/rdf-schema#label" />
  <rdfs:domain rdf:resource="http://usefulinc.com/ns/doap#" />

That means:

* the exactURI <http://projects.apache.org/ns/asfext#pmc> (or abbreviated
as asfext:pmc if the prefix declaration is available) defines the property
name, exactly "pmc", other syntactic version would not match the formal
* the label is just the human-readable label of the property, can't be use
as property
* comment is the same, just a comment to be read
* subproperty means that the value of the property has a specialized
meaning over the general purpose label
* domain is the type of objects that can use that property, in this case
doap:Project instances
*  range defines the values in ca take, int his case a literal, a basic
type, such as string or int

And that's more of less the semantics behind such definition of the
property. Hope it helps to understand.

> Also if it is possible to validate that the various RDF files are
> correct according to the formal definitions.
> PMCs could then submit their files for checking.

I think we can discuss that infrastructure for the new site. I'm happy to
help. Python provides the required libraries. I'll open a thread, probably


Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co

View raw message