Way back when, when people were all hot about XML and ontologies (c. 2000) there was the fantasy that one could define some sort of repository where all the "things" of the world were categorized, organized, and named based on some sort of standardized set of attributes and categories. The fantasy died a slow death throughout the 00's because it turns out that names, categories and attributes are quite political and context specific. Standards like these are VERY dependent on the community that uses them. The community is important because the right attributes and categories depend on what is salient for that community.
If you want to get a sense of how complicated this gets take a look at WordNet. If you use the search page to look up "lamp", you will get two sense listings. Click on any of the sense listings and you will get a listing of all of the superclasses (hypernyms) and subclasses (hyponyms). There are quite a lot for "source of artificial illumination". The "piece of furniture" sense has fewer, but I suspect the list is incomplete. If a lamp marketing guru were to take the time to enter in all of their favorite product categories for lamps the list of hyponyms would be a lot longer.
Although the lists of hyponyms and hypernyms doesn't directly give you your list of attributes, it should illustrate the scale of the problem: each of those hypernyms and hyponyms potentially has its own list of important attributes. If you pick any two hyponyms, sometimes the attribute lists will overlap and sometimes they will conflict. Any "standard" would have to pick a mutually consistent set of standard hypernyms and hyponyms and then plumb them for attributes.
If you really do want to come up with some standard, you have to first define your community of concern: whose notion of lamp are you trying to define? Even ISO standards for electrical equipment don't pretend to define every aspect of electrical equipment. Rather they define whatever is important for the particular kind of engineering problem its user community needs to address. Same thing with genetic information data, wellbore data, electronic automated design data, financial data, etc. etc. IF you have a clear idea of a community, you MIGHT be able to find a business association that has created a standard. But without a community to name its important categories of lamp (hyponyms, hypernyms) you can't even begin to guess at what the standard attributes should be.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||