YuCROWN Corporation 合作討論稿 ・ 小船 Station 由 YuCROWN 製作,Earth LinC 由 Kong Group 提供與營運,Kong Group 透過 Earth LinC 提供技術支援 YuCROWN Corporation collaboration discussion draft · Station by YuCROWN · Earth LinC provided and operated by Kong Group, which provides technical support through Earth LinC

小船觀測資料接入說明 Little Boat ObservationsData Intake Guide

本合作討論稿由美國 501(c)(3) 非營利組織 YuCROWN Corporation 提出,小船 Station 由 YuCROWN 製作。Earth LinC 由 Kong Group 提供與營運,Kong Group 透過 Earth LinC 為本專案提供技術與資源支援,旨在與鴻海/NBS 專案共同推進觀測資料的公眾呈現與教育應用。 This collaboration discussion draft is put forward by YuCROWN Corporation, a U.S. 501(c)(3) nonprofit organization. The small-boat Station is made by YuCROWN. Earth LinC is provided and operated by Kong Group, which provides technical and resource support for this project through Earth LinC. Together they propose collaborating with Hon Hai / the NBS project to advance the public presentation and educational use of observational data.

把經授權的船上觀測,接成兩船航跡、歷史回放,以及學生看得懂的回報。 Turn authorized onboard observations into two boat tracks, history playback, and reports students can understand.

  • 草案DRAFT
  • 示例模式 ・ 非實測SAMPLE MODE · NOT MEASURED
  • 真實觀測接入待技術對接確認LIVE DATA INTAKE PENDING COORDINATION
查看小船 →Explore the Boats →
  1. 船上設備Onboard devices 專案 IT ・ 設備清單待確認Project IT · device list to confirm
  2. 衛星/供應商接收Satellite / provider receiving 專案 ITProject IT
  3. 專案資料庫Project database 專案 ITProject IT
  4. 經授權只讀 API 或資料輸出Authorized read-only API or data export 專案 IT ・ 公開接口Project IT · public interface
  5. 互動頁面Interactive page Earth LinC(Kong Group)・ 呈現與適配Earth LinC (Kong Group) · display & adaptation

此流程出自專案方的描述;實際由誰部署、維護適配服務,待雙方於技術對接時確認 This flow reflects the project side's description. Who deploys and maintains the adaptation service will be confirmed during technical coordination

DATA SECURITY後端憑證由接收服務保管,不嵌入頁面程式碼,亦不經由 AI 傳遞。Backend credentials are stored with the receiving service and never embedded in page code or passed through AI.

↓ UPDATE 最新安排請見「方案更新」;初始草案保留供參考,如有不同,以更新區塊為準。 For the latest arrangements see "Plan update"; the initial draft is kept for reference — where they differ, the update section takes precedence.

方案更新 ・ 2026-10-12 Plan update · 2026-10-12

方案更新|資料自動更新與雙向連結 Plan update | Automatic data updates and two-way links

本區塊記錄初始草案之後確認的方向與技術提案。標註「已確認方向」者為雙方認可的方針;標註「技術提案」者待技術對接確認,接入方式與接口規格將於協調過程中確定。 This section records directions confirmed and technical proposals made after the initial draft. Items marked "Confirmed direction" reflect agreed-on policy; items marked "Proposed" are subject to technical coordination — intake method and interface specifications will be confirmed during that process.

已確認方向Confirmed direction NBS 與 Station 雙向連結 Two-way links between NBS and the Station

已確認採用方案 A:NBS 官方網站(nbs-initiative.com)在適當位置放置截圖卡片或普通連結,指向實際的「小船,把海帶回來」Station(即使用者體驗頁面,不是本技術說明頁)。「小船 Station」中同時加入指向 NBS 網站的外連連結。iframe 嵌入目前不在範圍之內,為未來可選升級。

Option A is confirmed: the NBS official website (nbs-initiative.com) carries a screenshot card or ordinary link pointing to the actual "小船,把海帶回來" Station (the user-facing experience page, not this technical guide). The small-boat Station includes an outbound link back to the NBS website. iframe embedding is not in current scope and remains an optional future upgrade.

具體專案子頁面 URL、卡片尺寸、放置位置、開啟方式等細節,待與 NBS 管理方協調確認。

Specific project landing sub-page URL, card size, placement, and tab behavior remain to be coordinated with the NBS administrator.

目標Goal 接入後,觀測資料自動更新頁面 After intake: observations update the page automatically

接入實施後,每船的位置、航跡與感測值在 Station 中依約定頻率自動更新。已開啟的頁面依約定間隔重新整理,不需手動編輯或重新製作內容。頁面顯示觀測時間(observed_at)、接收時間(received_at)與目前資料狀態。

Once intake is implemented, each boat's position, track and available sensor values update automatically in the Station at the agreed frequency. An already-open page refreshes at an agreed interval without manual content edits or re-composition. The page shows observation time (observed_at), reception time (received_at), and current data status.

資料依約定頻率自動更新,更新時效取決於船上回報與傳輸延遲。目前真實觀測尚未接入;本提案由 YuCROWN Corporation 提出,Earth LinC 由 Kong Group 提供與營運,Kong Group 透過 Earth LinC 提供技術支援。

Data updates automatically at the agreed frequency; timeliness depends on onboard reporting and transmission delay. No live observations are connected yet. This proposal is put forward by YuCROWN Corporation; Earth LinC is provided and operated by Kong Group, which provides technical support through Earth LinC.

技術提案Proposed 接入架構提案 Proposed intake architecture

提案流程:專案資料來源 → 鴻海/專案伺服器 → Earth LinC 後端接收、驗證與儲存 → 「小船 Station」同域讀取。以下兩種接入方式均為提案,待雙方依資安政策與接口條件確認:

Proposed flow: project data source → Hon Hai / project server → Earth LinC backend receiving, validation and storage → small-boat Station reads from same domain. Both intake approaches below are proposals; both teams will confirm based on security policy and interface conditions:

  • 推送(優先評估):由鴻海伺服器定期推送 JSON 至 Earth LinC 接收端。此時,專案伺服器保管 Earth LinC 接收服務的認證憑證。
  • Push (preferred starting point): Hon Hai server periodically pushes JSON to the Earth LinC intake endpoint. In this case the project server holds the Earth LinC receiving-service credentials.
  • 拉取(備選):若貴司網路政策不允許主動外送,可改由 Earth LinC 後端定期讀取經授權的唯讀接口。此時,Earth LinC 後端保管對方提供的唯讀接口憑證。
  • Pull (fallback): if Hon Hai network policy does not permit outbound delivery, Earth LinC backend can instead periodically fetch from an authorized read-only interface. In this case Earth LinC backend holds the read-only interface credentials provided by the project.

所有憑證均不嵌入頁面程式碼或傳送給 AI。兩種方式均不要求存取對方的資料庫;接入方式與接口規格待技術對接確認。

All credentials are never embedded in page code or passed through AI. Neither approach requires database-level access to the other side's systems; intake method and interface specifications will be confirmed during technical coordination.

Station 從 Earth LinC 自有域名讀取資料,而非每位訪客的瀏覽器直接呼叫外部鴻海 API。接口端點、認證方式、字段對應、回報/推送/重整間隔、重試與去重處理,均於技術協調時確認。

The Station reads from Earth LinC's own domain rather than each visitor's browser calling an external Hon Hai API directly. Endpoint, authentication, payload mapping, reporting/push/refresh intervals, retries and duplicate handling are all confirmed during technical coordination.

技術提案Proposed 資料管理安排 Data management arrangement

Earth LinC 後端的實際資料儲存位置、保存期限與刪除方式,由技術雙方確認。動態觀測記錄保存在可管理的後端儲存空間,與 Station 頁面內容分開;原始觀測記錄不寫入頁面本體或永久發布版本。頁面僅依授權範圍讀取並呈現資料。以上為實施安排,待雙方協調後確認,目前尚未部署。

The actual storage location, retention period and deletion method for data held in Earth LinC's backend will be confirmed by both technical teams. Dynamic observation records are kept in manageable backend storage, separate from the Station page content; raw observation records are not written into the page body or any permanently published version. The page only reads and displays data within the authorized scope. These are implementation arrangements to be confirmed through coordination and are not yet deployed.

沿用規則Preserved rules 字段規則,更新後仍完整沿用 Field rules remain fully in force after this update

以下規則不因本次更新而改變:以 boat_id 區分兩船;observed_at ≠ received_at;缺測為 null 不是 0;單位與 source 明確標出;軌跡推算速度不等於海流;示例資料與實測資料明確區分。詳細定義見下方「字段辭典」。

The following rules are unchanged by this update: separate boats by boat_id; observed_at ≠ received_at; missing is null not 0; unit and source always explicit; track-derived speed is not ocean current; sample data clearly distinct from live data. See the Field dictionary below for full definitions.

技術提案Proposed 提案分工 Proposed division of responsibilities

YuCROWN Corporation:合作討論稿提案方(美國 501(c)(3) 非營利組織),負責小船 Station 的內容製作與教育應用協調。
Earth LinC(Kong Group):負責接收端開發、技術接入、Station 顯示與技術支援;由 Kong Group 提供與營運。
鴻海 IT:負責資料來源、授權及約定交付方式。
NBS 管理方:負責其平台上的截圖卡片或連結。

YuCROWN Corporation: proposal originator (U.S. 501(c)(3) nonprofit); responsible for small-boat Station content and educational collaboration coordination.
Earth LinC (Kong Group): responsible for intake development, technical support, Station display and hosting; provided and operated by Kong Group.
Hon Hai IT: responsible for the data source, authorization and agreed delivery method.
NBS administrator: responsible for the card or link on their platform.

觀測資料自動更新;系統維護、異常處理與內容更新由雙方依分工協調。持續維護範圍、部署安排與異常聯絡窗口,待協議後確認。

Observational data updates automatically; system maintenance, incident handling and content updates are coordinated between both teams according to agreed responsibilities. Ongoing maintenance scope, deployment and incident contacts are to be agreed.

補充驗收Additional acceptance 本次更新新增的驗收項目 Acceptance items added by this update
  • 新收到的有效記錄,在已開啟的頁面內於約定重整間隔內出現。
  • A newly received valid record appears in an already-open page within the agreed refresh interval.
  • 各船數值與歷史航跡正確。
  • Per-boat values and history are correct.
  • 中斷時,保留最後一筆有效儲存的回報並標示時間戳與狀態;不補造觀測資料。
  • Interruptions keep the last valid stored report with timestamp and status; no observations are fabricated.
  • 雙向連結在手機、iPad 與桌機上均可使用。
  • Two-way links work on phone, iPad and desktop.
  • 示例模式與真實資料模式明確區分。
  • Sample mode and live data mode are clearly distinct.
技術提案Proposed 專案短網址(提案) Project short URL (proposal)

earthlinc.earth/專案名稱 等短網址為指向同一 Station 的別名提案,名稱與設定待技術對接時確認,目前尚非有效連結。

A short URL such as earthlinc.earth/project-name is a proposed alias pointing to the same Station; name and configuration are pending technical coordination and it is not yet a live link.

下一步(更新後)Next steps (post-update)

請提供:一份去敏真實樣本;設備、字段與單位清單;回報頻率、預期延遲、歷史範圍與可公開範圍;確認伺服器推送或唯讀接口的可用條件;以及 NBS 確切目標 URL 與卡片需求。雙方再進行技術協調、實施與測試接入。

Please provide: one de-identified actual sample; device, field and unit list; reporting frequency, expected delay, history scope, and public scope; confirm server push or read-only interface availability; and the exact NBS target URL and card requirements. Both teams then coordinate, implement and test the intake.

目標與範圍Aim & scope

先把位置與時間接通Get position and time right first

以下為初始草案,供參考。如與上方「方案更新」有不同,以更新區塊為準。The following is the initial draft, kept for reference. Where it differs from the "Plan update" above, the update section takes precedence.

目標Aim

把經授權的觀測,轉成兩船航跡、歷史回放與學生可理解的回報。Convert authorized observations into two tracks, history playback and student-readable reports.

第一階段Phase one

位置與時間優先;其餘感測值依實際設備確認。Position and time first; other sensor values depend on the actual devices.

更新頻率與對接事項Update frequency and coordination

資料依約定頻率自動更新,更新時效取決於船上回報與傳輸延遲;具體頻率於技術對接時確認。Data updates automatically at the agreed frequency; timeliness depends on onboard reporting and transmission delay. The specific interval will be confirmed during technical coordination.

本頁範圍說明Scope of this page

本頁提供接入規劃與欄位示例;實際設備、接口與更新頻率於技術對接時確認。示例資料僅供欄位對照,真實觀測接入後另行驗證。目前真實觀測尚未接入。本頁為獨立的合作討論稿,與現有「小船,把海帶回來」分開維護。 This page provides intake planning and field examples; actual devices, interfaces and update frequency will be confirmed during technical coordination. Sample data is for field reference only; live observations will be verified separately after intake. No live observations are connected at this time. This page is a standalone collaboration discussion draft, maintained separately from the existing "小船,把海帶回來".

四個示意區 ↔ 對應字段Four zones ↔ matching fields

點一個區,看它需要哪些欄位Pick a zone, see the fields it needs

左側是示意,右側是它依賴的字段。所有畫面內容都是示例,非實測。The sketch on the left, the fields it relies on at right. Everything shown is an example, not measured.

航跡Track

sample-boat-01 sample-boat-02 observed_at →

示意,非實測 ・ 實線/虛線=兩條各自的船SKETCH, NOT MEASURED · solid / dotted = two separate boats

字段Field需求Need用在哪Used for
boat_id必需must兩船各畫各的線,不串資料。Keeps each boat's line separate.
observed_at必需must航跡點的排序與歷史回放,依量到的時間,不依到達順序。Orders points and drives playback — by measurement time, not arrival order.
latitude
longitude
必需must每個點的位置,WGS84 十進制度(待確認)。Each point's position, WGS84 decimal degrees (to confirm).
source必需must標明點是船上定位,還是軌跡推算。Marks a point as onboard fix or track-derived.

回報卡片Report card

sample-boat-01onboard_sensor
observed_at2000-01-01T00:00:00Z
lat / lon0.0 / 0.0 (佔位)(placeholder)
temperaturenull ・ 缺測,不是 0missing, not 0

示意,非實測 ・ 給學生看的白話文案待共同設計SKETCH, NOT MEASURED · plain-language copy for students to be co-designed

字段Field需求Need用在哪Used for
boat_id
name
必需/建議must / suggestedboat_id 穩定識別;name 只是顯示名稱,可以更改。boat_id is the stable identity; name is just a display label and may change.
observed_at
latitude
longitude
必需must最新一次有效定位。The latest valid fix.
metric
value
unit
quality
依設備per device有感測器才有;缺測 value 為 null,並顯示「未測到」。Only if a sensor exists; a missing value is null and shows as "not measured".
source必需must卡片上清楚標明三種來源之一。Each value is tagged with one of three source types.

更新狀態Update status

正常Normal在預期延遲內within expected delay
延遲Delayedreceived_at 晚於預期received_at later than expected
暫無新資料No new data仍顯示最後有效回報last valid report still shown
observed_at2000-01-01T00:00:00Z
received_at2000-01-01T00:12:00Z

示意,非實測 ・ 門檻待 IT 提供正常頻率與延遲後再定SKETCH, NOT MEASURED · thresholds set after IT gives normal frequency and delay

字段Field需求Need用在哪Used for
observed_at必需must設備量到的時刻。When the device measured it.
received_at必需must系統收到的時刻。兩者之差是傳輸延遲,不能互換。When the system received it. The gap is transmission delay; never swap the two.
quality依設備per device品質標記;缺測與可疑值分開呈現。Quality flag; missing and suspect values are shown apart.
(無新字段)(no new field)—延遲不等於失聯:沒有新資料時,保留最後有效回報並標示時間,不誤報失聯。Delay is not loss: with no new data, keep the last valid report with its time; never report "lost" by mistake.

NBS 入口NBS entry

✓ 方式 A(已選定):卡片或普通入口連結 → Station✓ Option A (selected): card or plain entry link → Station
方式 B:嵌入互動頁面(未來可選升級,目前不在範圍)Option B: embedded interactive page (optional future upgrade, not in current scope)

示意,非實測 ・ 方案 A 已選定;具體子頁面 URL 與卡片細節待協調SKETCH, NOT MEASURED · Option A selected; specific sub-page URL and card details to be coordinated

項目Item需求Need用在哪Used for
public_scope必需must說明哪些資料、哪兩船可以公開。States which data and which two boats may be public.
boat_id必需must入口只展示被授權的船。The entry shows only authorized boats.
入口方式Entry method已選定 AA selectedNBS 官網卡片或連結 → Station;Station 加入指向 NBS 的外連。NBS official site card or link → Station; Station includes outbound link to NBS.
NBS 官網NBS official site已確認confirmednbs-initiative.com;專案子頁面 URL 待協調。; project sub-page URL to be coordinated.

字段辭典Field dictionary

建議交換的字段Suggested exchange fields

這些名字只是建議,用來對齊雙方的理解;不要求修改對方的資料庫,對應方式待雙方確認。These names are suggestions for aligning understanding. No one is asked to change their database; the mapping is for both sides to confirm.

字段Field需求Need說明Meaning
船識別Boat identity
boat_id必需must穩定、不隨改名而變的識別碼。A stable identifier that survives renaming.
name建議suggested顯示名稱,可變。Display name; may change.
位置(第一階段)Position (phase one)
observed_at必需must設備實際量到的時間。建議 ISO 8601 UTC,待確認。When the device actually measured. ISO 8601 UTC suggested, to confirm.
latitude必需must緯度,WGS84 十進制度,待確認。Latitude, WGS84 decimal degrees, to confirm.
longitude必需must經度,WGS84 十進制度,待確認。Longitude, WGS84 decimal degrees, to confirm.
接收Reception
received_at必需must系統收到記錄的時間,與 observed_at 分開。When the system received the record; kept apart from observed_at.
感測值(依設備能力)Sensor values (per device capability)
metric依設備per device量的是什麼,例如溫度。What was measured, e.g. temperature.
value依設備per device數值;缺測為 null,不是 0。The number; missing is null, not 0.
unit依設備per device單位,需明確寫出。The unit, always explicit.
quality依設備per device品質標記,取值待定。Quality flag; allowed values to be agreed.
來源與公開範圍Source & public scope
source必需must三種來源之一,見下。One of three source types, below.
public_scope必需must說明這筆資料可公開到什麼程度。How far this record may be made public.
onboard_sensor船上感測Onboard sensing
船上設備直接量到的值。Values measured directly by devices on the boat.
track_derived軌跡推算Track-derived
由位置變化算出,例如地面位移速度。Computed from position change, e.g. speed over ground.
external_env外部環境資料External environment
第三方風、海流等,後續另接。Third-party wind, current, etc.; connected later.

時間Time

建議 ISO 8601 UTC,例如 2000-01-01T00:00:00Z(示例);需對方確認。ISO 8601 UTC suggested, e.g. 2000-01-01T00:00:00Z (example); to be confirmed.

座標Coordinates

WGS84 十進制度;需對方確認。WGS84 decimal degrees; to be confirmed.

observed_at ≠ received_at

前者是量到的時刻,後者是收到的時刻;差值才是延遲。One is when it was measured, the other when it arrived; only their gap is delay.

缺測是 null,不是 0Missing is null, not 0

0 度是一個真實的數值;沒量到就是 null。0 degrees is a real reading; no reading is null.

船速不是海流Boat speed is not current

GPS 地面位移速度含船自身的移動,不等於海流。GPS speed over ground includes the boat's own motion; it is not ocean current.

外部資料另接External data comes later

風/海流等第三方資料需做時間與空間匹配,並取得來源授權;不冒稱為船上實測。Third-party wind/current needs time-space matching and source authorization, and is never passed off as onboard measurement.

  • boat_id
  • name
  • observed_at
  • received_at
  • latitude
  • longitude
  • metric
  • value
  • unit
  • quality
  • source
  • public_scope

示例 JSONSample JSON

三筆小例子,全部是示例Three small examples, all samples

兩個 boat_id 都是佔位名稱;座標、時間、數值均為虛構,不指向任何真實船名或放流位置。Both boat_ids are placeholders. Coordinates, times and values are invented and point to no real boat name or release location.

position 位置position

示例,非實測SAMPLE · NOT MEASURED
{
  "_mode": "sample",
  "_note": "示例,非實測",
  "boat_id": "sample-boat-01",
  "observed_at": "2000-01-01T00:00:00Z",
  "received_at": "2000-01-01T00:12:00Z",
  "latitude": 0.0,
  "longitude": 0.0,
  "source": "onboard_sensor",
  "public_scope": "sample_only"
}
座標為佔位值Coordinates are placeholders

temperature 溫度(可選)temperature (optional)

示例,非實測SAMPLE · NOT MEASURED
{
  "_mode": "sample",
  "_note": "示例,非實測",
  "boat_id": "sample-boat-02",
  "observed_at": "2000-01-01T00:00:00Z",
  "received_at": "2000-01-01T00:15:00Z",
  "metric": "temperature",
  "value": 20.0,
  "unit": "degC",
  "quality": "unchecked",
  "source": "onboard_sensor",
  "public_scope": "sample_only"
}
是否有此感測器待 IT 確認Whether this sensor exists: IT to confirm

缺測 missingmissing value

示例,非實測SAMPLE · NOT MEASURED
{
  "_mode": "sample",
  "_note": "示例,非實測;缺測是 null,不是 0",
  "boat_id": "sample-boat-02",
  "observed_at": "2000-01-01T01:00:00Z",
  "received_at": "2000-01-01T01:15:00Z",
  "metric": "temperature",
  "value": null,
  "unit": "degC",
  "quality": "missing",
  "source": "onboard_sensor",
  "public_scope": "sample_only"
}
頁面顯示「未測到」The page shows "not measured"

請 IT 先提供What we ask IT for first

七項東西,就能開始對照Seven things to start mapping

  • 一份去敏的真實樣本One de-identified real sample去掉敏感資訊,保留欄位結構與真實取值形態。Sensitive parts removed, real structure and value shapes kept.
  • 字段、單位與實際設備清單Fields, units and the actual device list有哪些欄位、什麼單位、哪些設備在回報。Which fields, which units, which devices report.
  • 資料取得方式How the data can be obtained伺服器推送 JSON,或提供唯讀接口供定期讀取;依貴司網路政策確認。Server push of JSON, or a read-only interface for periodic fetching; confirmed according to your network policy.
  • 正常回報頻率與延遲Normal reporting frequency and delay用來定出「延遲」與「暫無新資料」的門檻。Used to set the thresholds for "delayed" and "no new data".
  • 歷史可用範圍Available history range從何時起、能回放到多遠。From when, and how far back playback can go.
  • 讀取權限與可公開範圍Read permissions and what may be public誰能讀、哪些能對外展示。Who may read, and what may be shown publicly.
  • 技術聯絡窗口A technical contact由專案 IT 指定技術聯絡窗口。Project IT will designate a technical contact.

CSV 或 JSON 可以先用來驗證欄位對應,不一定要先建新 API。CSV or JSON can validate the mapping first — a new API is not necessarily needed up front.

接口細節(折疊)Interface details (collapsed)

待對接確認的技術事項Technical items for coordination

具體 URL、頻率、認證與部署全部於技術對接時確認;欄位草案為雙方對齊用的建議,不是既定規格。Concrete URLs, frequency, authentication and deployment are all confirmed during technical coordination. The field draft is a shared reference, not a fixed specification.

最新與歷史兩類需求Two kinds of request: latest and history

「最新」是每船最近一筆有效回報;「歷史」是依時間範圍取回的航跡。兩者是否走同一接口,待確認。"Latest" is each boat's most recent valid report; "history" is a track fetched by time range. Whether both use one interface is to be confirmed.

時間範圍查詢與分頁Time-range queries and paging

歷史以 observed_at 的起訖查詢;資料量大時需要分頁,每頁大小與上限待確認。History is queried by an observed_at start and end; large volumes need paging, with page size and limits to be confirmed.

穩定記錄識別與去重Stable record identity and de-duplication

每筆記錄需有穩定的識別方式,重送同一筆不應畫出重複的點。識別規則待確認。Each record needs a stable identity so a resend does not draw a duplicate point. The rule is to be confirmed.

遲到與更正記錄Late and corrected records

遲到的資料依 observed_at 放回正確位置。更正是覆蓋舊值還是另存新版本,待確認。Late data goes back in its observed_at slot. Whether a correction overwrites or is stored as a new version is to be confirmed.

限流與緩存Rate limits and caching

讀取頻率上限與緩存時間由專案 IT 決定,頁面依此調整,不繞過。Read-rate limits and cache time are set by project IT; the page adapts and does not work around them.

HTTPS、跨來源 CORS 與資料安全HTTPS, cross-origin CORS and data security

只走 HTTPS;跨來源(CORS)需設定允許的來源;後端憑證由接收服務保管,不嵌入頁面程式碼,亦不經由 AI 傳遞。HTTPS only; cross-origin (CORS) needs an allowed-origin setting; backend credentials are stored with the receiving service and never embedded in page code or passed through AI.

失敗時保留最後有效資料On failure, keep the last valid data

讀取失敗時,顯示最後一筆有效回報與它的時間,並標明狀態;不補造、不內插假資料。When a read fails, show the last valid report and its time with a clear status. Nothing is fabricated or interpolated.

NBS 整合NBS integration

初始方案比較|目前採用 AInitial options | A selected

目前已選定 A:NBS 以圖卡或連結通往小船 Station,Station 亦提供前往 NBS 的連結。以下保留初始方案比較;B 僅為未來可選升級。A is selected: NBS links to the small-boat Station via a card or ordinary link, and the Station links back to NBS. The initial comparison is retained below; B is only an optional future upgrade.

A 普通入口連結 已選定A · Plain entry link Selected

NBS 網站放一個連到互動頁面的連結。The NBS site carries a link to the interactive page.

待協調確認To coordinate

  • 連結放在哪、怎麼寫Where the link sits and how it reads
  • 在新分頁或同頁開啟Opens in a new tab or the same one

B 嵌入互動頁面 未來可選升級,目前不在範圍B · Embedded interactive page Optional future upgrade, not in current scope

以 frame 把互動頁面放進 NBS 的頁面裡。The interactive page sits inside an NBS page in a frame.

須核對Must check

  • 雙方的 frame / CSP 政策Both sides' frame / CSP policies
  • 容器尺寸Container size
  • 行動端表現Mobile behavior
  • 跨站限制Cross-site restrictions

未來如採用 B,雙方另行確認嵌入設定與多裝置測試。If B is pursued later, both teams will coordinate embedding settings and device testing.

nbs-initiative.com專案子頁面 URL 待協調Project sub-page URL to be coordinated

驗收清單Acceptance checklist

九件可以逐項打勾的事Nine things you can tick off

部署後的維護範圍、更新責任與異常聯絡窗口:待雙方約定Post-deployment maintenance scope, update responsibility and incident contact: to be agreed by both sides

雙方分工Who does what

各自的一半Each side's half

YuCROWN Corporation 合作討論稿提案方 ・ 美國 501(c)(3) 非營利組織 ・ Station 內容製作與教育應用協調Proposal originator · U.S. 501(c)(3) nonprofit · Station content & educational collaboration coordination

  • 負責小船 Station 的內容製作與教育應用協調Responsible for small-boat Station content and educational collaboration coordination
  • 提出本合作討論稿Originator of this collaboration discussion draft
  • 與鴻海/NBS 推進觀測資料的公眾呈現Proposes advancing public presentation of observational data with Hon Hai / NBS

Earth LinC 技術支援方(由 Kong Group 提供與營運)Technical support (provided & operated by Kong Group)

  • 由 Kong Group 提供與營運;Kong Group 透過 Earth LinC 為本專案提供技術與資源支援Provided and operated by Kong Group; Kong Group provides technical and resource support for this project through Earth LinC
  • 負責接收端開發、技術接入與 Station 技術支援Responsible for intake development, technical support and Station hosting
  • 把樣本對到欄位草案,回報差異Map the sample to the field draft and report differences
  • 頁面呈現與接入適配Page display and intake adaptation
  • 體驗測試:手機、iPad 與桌機;雙向連結;缺測與延遲狀態(若未來採用方案 B,另行協調嵌入測試)Experience testing: phone, iPad and desktop; two-way links; missing and delayed states (if option B is pursued later, embedding tests to be coordinated separately)
  • 後端憑證由接收服務保管,不嵌入頁面或經由 AI 傳遞;不改動對方資料庫Backend credentials stored with receiving service, never in page code or AI; does not alter the project database

鴻海 IT(專案 IT)Hon Hai IT (Project IT) 資料來源負責方Responsible for data source

  • 提供去敏真實樣本Provide the de-identified real sample
  • 提供字段、單位、設備清單Provide fields, units, device list
  • 說明取得方式、頻率、延遲、歷史範圍Explain access method, frequency, delay, history range
  • 決定讀取權限與可公開範圍Decide read permissions and public scope
  • 確認伺服器推送或唯讀接口的可用條件Confirm server push or read-only interface availability
  • 負責資料來源與授權交付方式Responsible for the data source and authorized delivery method
  • 指定技術聯絡窗口Designate a technical contact

待雙方確認To confirm together

  • 適配服務由誰部署與維護Who deploys and maintains the adaptation service
  • 接入方式(推送或拉取)與接口規格Intake method (push or pull) and interface specifications
  • Earth LinC 後端的資料儲存位置、保存期限與刪除方式Earth LinC backend storage location, retention period and deletion method
  • NBS 具體專案子頁面 URL 與卡片細節(官網:nbs-initiative.com 已確認)NBS specific project sub-page URL and card details (official site: nbs-initiative.com confirmed)
  • 維護、更新責任與異常窗口Maintenance, update duty, incident contact

下一步Next step

先對齊一份真實樣本First, align on one real sample

一份去敏的真實樣本,就足以驗證欄位對應,不必先建新 API。本提案由 YuCROWN Corporation 提出,Earth LinC 由 Kong Group 提供與營運,Kong Group 透過 Earth LinC 提供技術支援。One de-identified real sample is enough to test the field mapping — no new API needed first. This proposal is put forward by YuCROWN Corporation; Earth LinC is provided and operated by Kong Group, which provides technical support through Earth LinC.

此按鈕只會捲動到「請 IT 先提供」。本頁不送出任何資料、不收集憑證;請勿在此頁或與 AI 對話中貼上帳號、密碼或密鑰。This button only scrolls to "What we ask IT for first". The page sends no data and collects no credentials; never paste accounts, passwords or keys here or into an AI chat.