- From: Martin Hepp <martin.hepp@ebusiness-unibw.org>
- Date: Thu, 2 Sep 2010 16:23:53 +0200
- To: Bob Ferris <zazi@elbklang.net>
- Cc: semantic-web@w3.org
Hi Bob, yes, that's in theory. In practice, there will often be no direct interaction with the ontology labels, because the user interface is wrapped around the whole conceptual structures. Image the following scenario: - owners of car sales or rental sites add GoodRelations + VSO markup in RDFa to their page templates --> they will have to use the ontology identifiers in the code. It may be that future Web authoring tools will help with RDFa patterns and offer the ontology element labels, but in all "raw" coding with Vi or whatever, developers will have to deal with the identifiers. - applications will harvest and exploit the rich meta-data, filter / augment etc. them, and finally present them somehow to the user. But the applications won't use (and don't have to) display the labels attached to the elements in the ontology specification. They will use localized, context / application specific terminology. --> users will not even spot the ontologies used by the app to present the results. So I really think the multi-linguality of ontologies is overrated. Language tags are extremely powerful on the data level, though, for they simplify NLP processing / lifting. Martin On 02.09.2010, at 16:02, Bob Ferris wrote: > Am 02.09.2010 15:53, schrieb Martin Hepp: >> Hi Bob, >> yes, of course I use the proper language tag for the labels. However, >> given the state of tooling and typical workflows, the choice of the >> identifiers is still critical, because >> - RDFa coders will always use the identifiers and likely never see >> the >> labels >> - the navigation in the ontology documentation is typically based >> on the >> identifiers, not the labels. >> >> See http://purl.org/vso/ns >> >> In my ontology projects, I have so far refrained from providing >> translations for the elements, because the effort for reliable, >> high-quality translations is very high and the use is limited, >> given the >> fact that English is widely understood among application developers >> in >> the world. > > Well, the label can and should be used for the end user, and that's > why differ from its identifier. That means, a developer is then able > to directly re-use this label in his/her application. > > Cheers, > > > Bob >
Received on Thursday, 2 September 2010 14:24:24 UTC