km6 Special Interest Groups (SIG) hri07e
this Google site is a km6 deliverable under project hri07e (infofsys2).
2.0 Purpose:
Special Interest Groups (SIGs) have been defined within the context of project hri07e as a means of ensuring that interested, competent and externally recognized expertise is applied to technical and other knowledge domains for the prupose of defining the jargon and methods used within hri projects. Participation in a SIG is a way of sharing and presrving knowledge, but also a way of gaining recognition for expertise that is subject to not only hri review, but eventually the entire world.
While there are hundreds of potential SIG's and the tendency will be to create finer and finer sub-groups, there are probably less than one hundred useful groups - provided the experts can avoid some time honoured traditions of some academics who seem to have a tendency to create their own self promoting peer groups to idolize their founders.
There are four types of SIGs which are used in project hri07e - namely Primary, Secondary, Multidisciplinary or Special Purpose SIG's. The roles and contents of each are basically the same in format but vary in intensity.
3.0 Usage
Special Interest Groups are social groups who do more than just socialize - they create a number of physical and electronic artifacts as a result of their activites and existance. In the hri07e context a SIG will always result in;
- a website - in this case using the km6 CDID format and template
- a member's list
- a Data Dictionary
- SIG projects which are specila projects initited for the purposes of the SIG.
- other??
4.0 Frequency
5.0 References
6.0 Responsibility: Each hri07e SIG is first and foremost the responsibility of the "SIGmaster" for that domain of expertise. A (not-so) current list of SIG's is located here:
7.0 Ownership
8.0 Effort
9.0 Risks
10.0 Contents:
Project hri07 Special Interest Groups <sigs> under CDID:km6 are to be organized as follows:
10.1 Topics: <dd:km kc:topic>
Links and references for topics which are specific to the domain.
It usually occurs that "vendors", "orgs", "projects", "events", Key Codes", and training subjects will be identified in a topic page - often for the first time in the SIG's site. Where possible the significant entity should linked to the equivalent object in the SIG's site or a SIG site which is more appropriate for the term.
note: Topics Overload
note 2: Topics should not become OneNote or EverNote or "nonote" dumps (like they are now). They should be edited structures and complete - not places for thinking out loud (like they are now). There should be a OneNote/EvereNote dumpster for people to collect their thoughts before producing a topic - but it shouldn't be "Topics".
10.2 Resources: <dd:hr kc:res>
The SIG "resource" section can both "Human Resource" information about the SIG and other types of resources such as other organizations and special tools and equipment.
10.2.1 Human Resources
The Human Resources may include sections such as:
- Job Descriptions (hr1's) which are specific to the skills of the domain.
This also forms the SIG Registry which lists the members of the SIG by rank and status.
- Individual persons in a "who's who" type of list who have skills. These are typically described in resume's (hr2's) which should be located <somewhere>
NEW: Identify "Resources" who are familier with specific products for any vendor. For example:
<res X> -> Solidworks
<res Y> -> HaDoop mapReduce
10.2.2 Information Resources.
This is where academic publishers, trade journals, specialized websites, online data resources (including StatsCan) and such should be identified - where there interests are within the mandate of the SIG. Since "claiming" a trade journal to be the within the domain of the SIG - responsibility must be taken for posting and maintaining information related to that publication - or enabling others to do so.
Academic literature is particularly intended to link information via citations - and a measure of the valuse of an artcile has always been how many following articles reference it for one reason or another.
While reposting of articles is generally discouraged; fast and dependable recovery of reference articles may require local storage - in which case - it is recommended that articles only be stored once as attachments at this level at this location - or (better) - as Google documents under the project or SIG - with accessible links from this site.
An exception should be made for particularly obscure journals that have limited audiences - which should be stored with the project or topic (see 10.1 above) that generated them.
note: most "information" on the web is "vendor" information - i.e. an infomercial disguised as unbiased information - it should go where it belongs - in "vendors". This are should be third party independent information - if there is any such thing.
10.2.3 Organizational Resources
While most organizations with expertise in the domain should be located in the "Vendors" section (including non-profit trade and professional organizations) there may be commonly used services or tools which are important in the SIG domain which could be listed - examples might be:
- <can't think of one that wouldn't be in vendors or topics>
note: It will be expected that members of a SIG will also be members of the relevant professional organizations that support the body of knowledge - even (and especially) some of the more obscure ones. HRI depends upon the connections of its SIG members to connect beyond HRI and that the SIGs will provide HRI members with access (indirect perhaps - but access nonetheless) to organizations around the world in many languages. (Unfortunately - there is no method for paying the membership fees yet.)
10.2.4 Software
Useful SIG oriented software may exist independently of human resources or vendors and may be a useful section to add to the resources section of the SIG
10.2.5 Standards
Published Standards are a very important resource for most technical disciplines and may vary in number from a few to thousands (in the case of chemistry and electronics for example). It may be useful to point to both the obvious (eg: ISO) and the not so obvious ones (eg: ABYC small craft) that are useful to record for SIG users who may be involved in design activities or such.
10.2.6 Intellectual Property resources
Patents, Trademarks, Copyright, etc.
Patents are an excellent source of information in any give subject area and provide a linkage and therefore a very precise classification and chronology of the subject within very narrow parameters.
10.2.7 Financial Resources
Private and Government funding resources specialized to the SIG in question.
10.3 Events of interest <dd:?? kc:event>
- SIG sponsored conferences, lectures, webcasts, etc.
- domain related conferences, lectures, webcasts, etc.
10.4 Projects: <dd:pm kc:wo>
SIG-sponsored projects (work orders) which are for the benefit of teh SIG memebers specifically, but are NOT commercial projects.
10.5 CDID's: <dd:km kc:cdid>
Typical project deliverables and artifacts that may be produced by specialists working in the SIG's area of endeavour
R2 the CDIDs are the reports and presentation documents which are published as a result a work order being executed. They may or may not contain the entire data output of the effort - but usually will not; especially for engineering documents. the procedure(s) by which a CDID is produced may or may not be evident from the publication (usually not). For a given CDID there may be one or more procedures which have been executed to produce the document - and there may be procedures that have been borrowed from other CDI's and other SIG's.
10.6 Data Dictionary: <dd:km kc:dd>
r5:10.6 Data Dictionary
The Data Dictionary consists of two section - one for defining system and equipment code types for data sheet and system diagram tags and one for defining future data value and string key codes. The hope for both sets of codes is that automated procedures can use the data sheet tags to look up the data values for the data sheet elements and return the current values with a high confidence of traceability and chronology of the data values.
10.6.1 Equipment Tag Codes
These are the codes that the sig has recommended for all hri07e series System Diagrams and Data Sheets and should reflect industry standard usage where possible.
10.6.2 Data Sheet Key Codes
These are the codes that the sig is recommending for individual data values and data strings that are contained in Data Sheets. There are a few industry standards for these codes - but for the most part they will look like typical short form variable names in computer source code.
r4: 10.6 Data Dictionary Key Codes
Definitions and derivations of the important jargon and calculated values used within the domain.
r3: The Data Dictionary for a SIG is the "controlled vocabulary" for that domain as defined and enforced by the voting members of the SIG. For efficiency and configuration management purposes the collection of Data Dictionaries for an organization may be collected into one large km1 Data Dictionary but the responsibility for the accurate and executable definitions should not be removed from the SIG.
10.7 Vendors. <dd:acc kc:org>
this is not for project or hri member information - although it does not exclude them
- for hri accounts see the applicable ac110 account listing
Vendors who have products of specific interest in the domain.
- Legal Name
- URL's
- "about"
- also -
"Intellectual Property" holdings - such a patents & copyrights
This information is included in the SIG to assists with new projects that may be developing new technology or even for trademark infringement avoidance.
NEW: Identify "Resources" who are familier with specific products for any vendor. For example:
<res X> -> Solidworks
<res Y> -> HaDoop mapReduce
note: Due to the enormous size and dynamic nature of vendor information, It is recommended that only links be included along with enough information to give the SIG a feeling for what the company's offerings are. Specific projects will have data sheets that link specific instances of vendor information for a project but this may not be available beyond the project team and so project teams are encouraged to at least identify the vendors they have used that they expect to be used again in the SIG of their choice. This should be part of the Project archiving and clean-up task for any HRI project.
R1 10.8 Tutorials: <dd:edu kc:tutid>
R2 10.9 Procedures
R3 10.10 Tags
All entries in KM6's should be tagged with the origin date, location and owner of the original information (if known). Links to cited works should also be included.
It should be possible to view the topic or citation thread as a timeline (Google style)
11.0 MetaData
12.0 File Handling Policy