Template:EntityWiki Company v1/doc

From EntityWiki
Jump to navigation Jump to search

Purpose

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 1099, and adds explicit company, evidence, and mapping sections.

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.

Section coverage

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.

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.

Minimal invocation

{{EntityWiki Company v1
|record_status=Research draft — not independently verified
|entity_id=Not assigned
|official_website=https://www.example.com/
|schema_type=Organization
|last_reviewed=YYYY-MM-DD
|overview=Concise factual summary, with source references.
|company_identity=Legal name, public aliases and identifiers, when sourced.
|history=Not documented in reviewed sources.
|team=Public professional names and roles, when sourced.
|services=Service catalogue, each service with a source.
|products=Not applicable — explain the evidence for this conclusion.
|framework_title=Framework and methodology
|framework=Not documented in reviewed sources.
|locations=One subsection per verified branch; keep branch identity separate from the company.
|service_areas=Only explicitly documented service areas.
|google_business_profile=Not connected. Listing identity and categories require verification.
|external_links=Verified profiles about this company, with source references.
|ontology=Validated concepts and their typed relationships; do not treat topics as company identity.
|gallery=No publication-cleared media documented in reviewed sources.
|sources=Numbered source list, source revision/date, retrieval date and material conflicts.
}}

MAXPlaces reference example

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.

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's business coordinates.

Ontology and Google mapping rules

  • Company identity, branch identity, service/product classification and topical relationships are different relations.
  • Only exact, supported identity profiles belong in schema.org sameAs.
  • 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.
  • 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's selected primary category from a website description.
  • Listing Place IDs, business-profile resources, legacy map CIDs and map viewport coordinates are distinct fields. Do not manufacture one from another.
  • 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.

Publishing contract

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.

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.

Retrieved from "https://entitywiki.org/index.php?title=Template:EntityWiki_Company_v1/doc&oldid=1198"