Template talk:Concept

Properties

rdfs:range

Include rdfs:range? --Andreas Plank 17:22, 29 August 2012 (CEST)

imported from / is defined by

{{concept
…
|imported from      = property: imported from         → doesn't it replaces rdfs:isDefinedBy ?
|is defined by      = property: rdfs:isDefinedBy
…
}}

The use cases probably overlap? imported from is a semantic-mediawiki-property designed to put a page from the Wiki (definitely a "property:", probably but untested, also classes=categories) into another namespace, i.e. the RDF exports with namespace/URI. Question: Is the use of imported from always identical to is defined by? Note: on a property page we would need “imported from” but set once there it does not need to be set again elsewhere. At present both fields are in the template and forms, but it would be nice to simplify this.

--Andreas Plank 10:39, 6 September 2012 (CEST)

Agree, it sounds like a very good solution to reuse the "imported from" property as the value for rdfs:isDefinedBy --Dag Endresen 14:45, 10 September 2012 (CEST)

Default automatic categories

What default categories should we set for pages using the Concept template?

• Always "Category:skos:Concept". Or "Category:Concept"?
  • Notes: concept scheme and concept collection templates will set “Category:skos:Collection” an “Category:skos:ConceptScheme” etc.

    Question: "category: skos:ConceptScheme" / "category:skos:Collection" or “category: Concept scheme” / “category: Concept”? --Andreas Plank 18:12, 7 September 2012 (CEST)

• If "imported from:" is set for a concept, then set a "Category:imported concept" (old version used"Category:imported term")?
• Should for the values in concept scheme: automatic categories be set? Example: "Category:DarwinCore".
• Should for the values in concept collection: automatic categories be set? Example: "Category:Audubon Core Managment Vocabulary".
• is it correct to define [[Has default form::…]] on category: skos:Concept ?

It is not strictly necessary to set a category for each of these, since the properties can be queried in ask-queries and we can add filters also on Special:BrowseData.

--Andreas Plank 11:35, 6 September 2012 (CEST)

I believe we discussed that a term/concept reused in multiple skos:ConceptScheme (concept vocabularies) would be declared only once by one single Wiki page. When the skos:ConceptScheme is a single-value option in the Concept template edit form, each concept can only be in one single ConceptScheme? E.g. dcterms:accessRights is declared as in DublinCore, while this Concept should be included in both DublinCore and in DarwinCore...? There is a difference in the meaning between rdfs:isDefinedBy and skos:inScheme (I will look for the SKOS documentation page where I read about this difference). --Dag Endresen 15:30, 10 September 2012 (CEST)

Alistair Miles wrote on 6 Nov 2007 about the difference between rdfs:isDefinedBy and skos:ConceptScheme, http://lists.w3.org/Archives/Public/public-swd-wg/2007Nov/0011.html, and http://www.w3.org/2006/07/SWD/wiki/SkosDesign/ConceptSchemes/DiscussionPiece Here Alistair Miles discusses whether a skos:Concept can be in only one skos:ConceptScheme, or if it can be included in more than one. --Dag Endresen 16:56, 10 September 2012 (CEST)

Both Darwin Core and Audubon Core actually include terms/concepts from other concept vocabularies such as Dublin Core. It seems like Darwin Core and Audubon Core imports only some Dublin Core terms/concepts and not "all" of Dublin Core... How do we express this? I believe as mentioned that skos:Collection is only intended as an organizing or grouping principle within a skos:ConceptScheme and would therefore not be suitable to express this, or...? --Dag Endresen 16:56, 10 September 2012 (CEST)

Translations

Experiments how it can best be set correctly (no feedback necessary at the moment):

1. #subobject is more appropriate, because it creates a hash id on a page, that has to be set manually, e.g. page#en or the following proposal, e.g. “page#propertyName@en”. #set_internal uses only integer hash ids.
   • what should export in RDF? Proposal: a syntax like "propertyName@ISO-lang-code" as a subproperty of propertyName?
   • technical note: in a wiki page “#propertyName@en” will always be ancorencoded: {{anchorencode: propertyName@en}} returns “propertyName.40en” (that is {{urlencode: propertyName@en}} and replace “%” by “.”)

--Andreas Plank 12:12, 6 September 2012 (CEST)