User:Dvmorris/Architecture firm

From Archiplanet

Jump to: navigation, search

This page contains ideas on how to change Archiplanet's wiki into a semantic wiki by adding attributes and relations to each architecture firm article.

Contents

[edit] Precedent Templates for Architecture Frims

[edit] Archiplanet

Click here to view the existing Architecture firm info template on archiplanet's wiki. It looks like this:

{{Architecture Firm Info
|firm=
|people=
|address=
|city=
|state=
|state_abbreviated=
|zip=
|country=
|phone=
|fax=
|email=
|url=
|aw_directory_id=
}}

[edit] Wikipedia

Here is the existing Architect template from wikipedia. It looks like this more or less:

{{Infobox Architect
|image=
|caption=
|name=
|nationality=
|birth_date=
|birth_place=
|death_date=
|death_place=
|practice_name=
|significant_buildings=
|significant_projects=
|awards=
|}}
<nowiki>

==Work==

===Buildings===
<!--Example format
*Most Holy Trinity in Lyttelton, 1851 (demolished)
*Canterbury Provincial Council Buildings, 1858–1865: [http://www.ccc.govt.nz/Christchurch/CanterburyProvincialCouncilChambers/History/]
-->
===Projects===

===Awards===

==Resources==

===See also===

===Notes===

===References===
<div class="references-small">
<!--Example format
*Mclintock, A.H. (ed). "Mountfort, Benjamin Woolfield" (1966), ''An Encyclopaedia of New Zealand''.
-->
</div>

===External links===
<!--Example format
*[http://wheteveryourlinkis A description of the link]. Retrieved month day, year.
-->

<!--Example format
[[Category:1821 births|Blogs, Joe]]
[[Category:1941 deaths|Blogs, Joe]]
[[Category:English architects|Blogs, Joe]]
-->

</nowiki></pre>

[edit] Wikicompany Companybox template

and here is a template example from wikicompany. At this time, I am not sure how the Template:Logo template works on this page, but it would be interesting to include this on the architecture firm pages, in case a firm has a logo or some kind of representative image. Other things to note here are the links= and sub= sections, where there are multiple relations or links separated by commas. There must be a better way to handle this to keep the user from having to learn more complex wiki text formats. Perhaps this comma separated list could be split up in the template and output wtih the proper wiki format.

{{companybox|name=Rabobank Bank N.V.
[[Image:{{logo}}]]
|color=white
|bgcolor=black
|address=PO Box 17100, 3500 HG [[region:=Utrecht|Utrecht]], [[region:=Netherlands|Netherlands]]
|web=http://www.rabobank.com
|email=[mailto:info@rabobank.com info@rabobank.com]
|phone=[callto://+31-30-216-0000 +31 30 216 0000]
|fax=
|geocode=<geo>52.0913;5.1227</geo>
|type=[[of type:=services]]
|founding=[[founding:=1896]]
|employees=
|stock=
|links=[http://www.rabobankamerica.com Rabobank America], [http://www.raboagservices.com Rabo AgServices]
|jobs=
|products=
|parents=
|sub=[[sub::Valley Independent Bank]], [[sub::ACCBank]]
|aff=
|partners=
|customers=
|competitors=[[competitor::ABN AMRO]], [[competitor::ING Group]], [[competitor::Postbank Netherlands]]
}}

[edit] Semantic Architecture Firm Pages

  • It can be confusing to decide which parts of a page should be stored as an attribute or a relation. Many of these are up for discussion, and others have issues that are noted in the table below.

[edit] Possible Semantic Attributes

Attributes are descriptions of the characteristics of an object. For more info on Attributes, click here.

Attribute Name Data Type Description
Attribute:Architect name Type:String full name of architect (same as the page name)
Attribute:Architecture firm Type:String full name of architecture firm (same as the page name)
Attribute:Also known as Type:String if a firm or person has multiple names or nicknames

Contact info

Attribute:Employee Type:String listing important employees of the firm, could contain many. could also be stored as Relation:Has employee or for an architect template Relation:Employee of. These would be inverse relations. This is an important concept to keep in mind.
Attribute:Phone Type:String phone number for the firm, will use the [callto://+123456789] template.
Attribute:Fax Type:String fax number, could also use the [callto://+123456789] template.
Attribute:Web Type:String web address, obviously for linking to the firm's webpage.
Attribute:Email Type:String email address, will be put in the template page like this - [email:=example@example.com]. Here is another example of the email attribute from ontoworld.

Time

- see [1] for a discussion of representing years semantically
Attribute:Founding Type:Integer to describe the year a firm started. See also Relation:Founded in.
Attribute:Disbanded in Type:Integer if the firm no longer exists, the year it stopped... existing? the wording of this one should change, i just can't think of anything good at the moment. see also Relation:Unfounded in ???

Time

- see [2] for a discussion of representing years semantically
Attribute:Founding Type:Integer to describe the year a firm started. See also Relation:Founded in.
Attribute:Disbanded in Type:Integer if the firm no longer exists, the year it stopped... existing? the wording of this one should change, i just can't think of anything good at the moment. see also Unfounded in ???

Other Attributes

Attribute:AW Directory ID Type:Integer not sure what this is, but it's in the archiplanet wiki already, and it wouldn't hurt to keep it in here as a semantic attribute. i assume AW stands for Architecture Week.

[edit] Possible Relations

Relations are machine-processable descriptions of relationships between wiki articles. Read here for more info on relations. Many of the examples below could possibly serve the purposes of the Archiplanet wiki better as Attributes.

Relation Name Description

General

Relation:Designed to link to the building article of a building the firm designed. could be the same as Built
Relation:Is famous for link to a building the firm or architect is famous for.
Relation:Has employee to link to a person article about a significant employee
Relation:Founded in link to year article when the studio was founded.

Location

Relation:Has location country self-explanatory
Relation:Has location state self-explanatory
Relation:Located in a place, not necessarily a city name or country name, but a place with an article
Relation:Has location city needs to be discussed... the differences b/w using city as an attribute vs. using it as a relation
Relation:Has location US county could possibly add other more detailed geographic info, such as county, region, province, street, district, etc...

[edit] Other Ideas

  • using the wikipedia template like on wikicompany.
  • custom parser functions like wikicompany to pull in extra info about an architecture firm, like an rss feed or something else significant, like news articles via news.google.com.
  • linking to wikicompany of course.
  • linking to greatbuildings page as archiplanet already does.
  • embedded google map for a specific page, and special google maps pages that map groups of firms or buildings
  • ajax plugin with a date or region slider to show lists of architects or buildings from a certain period of time or near a certain location.