<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://entitywiki.org/index.php?action=history&amp;feed=atom&amp;title=Template%3AEntityWiki_Company_v1%2Fdoc</id>
	<title>Template:EntityWiki Company v1/doc - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://entitywiki.org/index.php?action=history&amp;feed=atom&amp;title=Template%3AEntityWiki_Company_v1%2Fdoc"/>
	<link rel="alternate" type="text/html" href="https://entitywiki.org/index.php?title=Template:EntityWiki_Company_v1/doc&amp;action=history"/>
	<updated>2026-10-29T15:16:09Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.1</generator>
	<entry>
		<id>https://entitywiki.org/index.php?title=Template:EntityWiki_Company_v1/doc&amp;diff=1198&amp;oldid=prev</id>
		<title>Entitywikiadmin: Document profile parameters, section coverage, source requirements, and typed ontology/GBP mapping</title>
		<link rel="alternate" type="text/html" href="https://entitywiki.org/index.php?title=Template:EntityWiki_Company_v1/doc&amp;diff=1198&amp;oldid=prev"/>
		<updated>2026-10-23T15:33:00Z</updated>

		<summary type="html">&lt;p&gt;Document profile parameters, section coverage, source requirements, and typed ontology/GBP mapping&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Purpose ==&lt;br /&gt;
This is the first reusable company profile shell for the SchemaBrains-to-EntityWiki integration. It preserves the six top-level sections in [[MAXPlaces Marketing]] revision [https://entitywiki.org/index.php?title=MAXPlaces_Marketing&amp;amp;oldid=1099 1099], and adds explicit company, evidence, and mapping sections.&lt;br /&gt;
&lt;br /&gt;
The shell is available for manual and future agent-generated entries. It does not itself run a scraper, call SchemaBrains, publish JSON-LD, connect Google, or schedule updates.&lt;br /&gt;
&lt;br /&gt;
== Section coverage ==&lt;br /&gt;
Every invocation renders 14 sections: Overview, Company identity, History, Team, Services, Products and offers, Framework and methodology, Locations, Service areas, Google Business Profile mapping, External links, Ontology, Gallery, and Sources and record history.&lt;br /&gt;
&lt;br /&gt;
For each section, the proposed integration must record one of: sourced, needs research, conflicted, not applicable with a reason, or withheld with a reason. A section with a default message is represented but is not verified or publication-ready. Do not invent a founding date, leadership title, product, address, listing ID, category, rating, or ontology match to make a section look complete.&lt;br /&gt;
&lt;br /&gt;
== Minimal invocation ==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
{{EntityWiki Company v1&lt;br /&gt;
|record_status=Research draft — not independently verified&lt;br /&gt;
|entity_id=Not assigned&lt;br /&gt;
|official_website=https://www.example.com/&lt;br /&gt;
|schema_type=Organization&lt;br /&gt;
|last_reviewed=YYYY-MM-DD&lt;br /&gt;
|overview=Concise factual summary, with source references.&lt;br /&gt;
|company_identity=Legal name, public aliases and identifiers, when sourced.&lt;br /&gt;
|history=Not documented in reviewed sources.&lt;br /&gt;
|team=Public professional names and roles, when sourced.&lt;br /&gt;
|services=Service catalogue, each service with a source.&lt;br /&gt;
|products=Not applicable — explain the evidence for this conclusion.&lt;br /&gt;
|framework_title=Framework and methodology&lt;br /&gt;
|framework=Not documented in reviewed sources.&lt;br /&gt;
|locations=One subsection per verified branch; keep branch identity separate from the company.&lt;br /&gt;
|service_areas=Only explicitly documented service areas.&lt;br /&gt;
|google_business_profile=Not connected. Listing identity and categories require verification.&lt;br /&gt;
|external_links=Verified profiles about this company, with source references.&lt;br /&gt;
|ontology=Validated concepts and their typed relationships; do not treat topics as company identity.&lt;br /&gt;
|gallery=No publication-cleared media documented in reviewed sources.&lt;br /&gt;
|sources=Numbered source list, source revision/date, retrieval date and material conflicts.&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== MAXPlaces reference example ==&lt;br /&gt;
The reference has nine legacy service subsections, two locations, 30 external profile links and 65 ontology links. These counts describe revision 1099; they are not verified-current business facts. Its custom S.T.A.R. section can be retained with the framework_title parameter. Other companies must use their own documented methodology, if any.&lt;br /&gt;
&lt;br /&gt;
The October 23, 2026 research found differences between the legacy entry and current company pages, including a New York postal-code disagreement and changed service/framework wording. Those claims require reconciliation before publication. Map viewport coordinates are not proof of the listing&amp;#039;s business coordinates.&lt;br /&gt;
&lt;br /&gt;
== Ontology and Google mapping rules ==&lt;br /&gt;
* Company identity, branch identity, service/product classification and topical relationships are different relations.&lt;br /&gt;
* Only exact, supported identity profiles belong in schema.org sameAs.&lt;br /&gt;
* Product Ontology class identifiers use http://www.productontology.org/id/ followed by a validated English Wikipedia concept title. A derived URL is a candidate until semantic fit and availability have been checked. The /doc/ URL is a document view.&lt;br /&gt;
* Google Business Profile category IDs and Places types are separate vocabularies. Store the category resource ID and mapping version when legitimately obtained; do not infer a listing&amp;#039;s selected primary category from a website description.&lt;br /&gt;
* Listing Place IDs, business-profile resources, legacy map CIDs and map viewport coordinates are distinct fields. Do not manufacture one from another.&lt;br /&gt;
* Long-term public facts should come from company-owned pages, owner attestations or other permitted sources. Google API content requires its own applicable access, caching, display and attribution treatment.&lt;br /&gt;
&lt;br /&gt;
== Publishing contract ==&lt;br /&gt;
Future unattended writes must use an authorized server-side MediaWiki integration, revision conflict checks, source references, stable entity IDs, idempotent publication receipts and read-after-write verification. Preserve manual edits and unrelated page sections. Missing or conflicting facts go to a review queue. The research template does not grant a bot credential or access to another website.&lt;br /&gt;
&lt;br /&gt;
Generated parameter values must be serialized as controlled wikitext; do not insert raw scraped HTML, scripts, untrusted template syntax or arbitrary iframe URLs. This shell intentionally requires no ParserFunctions, Scribunto, Cite, Semantic MediaWiki or Wikibase extension.&lt;/div&gt;</summary>
		<author><name>Entitywikiadmin</name></author>
	</entry>
</feed>