项目和 Beacon 所有权规则改变了吗？
Projects and Beacon Ownership rules changed?
我上次与 Nearby 和 Proximity API 合作是在今年 7 月，并且根据 docs (last update Fev. 2017):
Any beacon you register with the Proximity Beacon API is associated
only with the project under which it was registered. Once registered
with a project, the only way to move a beacon to another project is to
give the beacon hardware a new beacon ID using the provisioning
software from the beacon manufacturer, and then register the beacon
with the new project.
如果我没记错的话，将信标添加到信标仪表板时，可以仅将附件添加到添加了信标的项目。我可以配置命名空间、类型和数据。
今天我不得不配置另一个项目，令我惊讶的是，当我在附件选项卡中时，我可以选择一个不同的项目来添加该附件，并且命名空间不再是可编辑的（默认情况下给出，它类似于项目编号）。
这是否意味着我可以拥有一个 "My beacons global project" 然后配置其他项目的附件？我已经进行了测试，附件已按配置交付给其他项目。
同时发生了什么变化，还是我从一开始就错过了这个？
谢谢你的时间。
By default, your project's namespace visibility is set to UNLISTED, so
its attachments are served only to your project, not to other
developers' projects.
A single beacon can support multiple attachments in different
namespaces, added by different projects using the Proximity Beacon
API's IAM roles. Each project controls the visibility of its
namespace, so it is possible for a single beacon to support a mixture
of public and unlisted attachments.
我上次与 Nearby 和 Proximity API 合作是在今年 7 月，并且根据 docs (last update Fev. 2017):
Any beacon you register with the Proximity Beacon API is associated only with the project under which it was registered. Once registered with a project, the only way to move a beacon to another project is to give the beacon hardware a new beacon ID using the provisioning software from the beacon manufacturer, and then register the beacon with the new project.
如果我没记错的话，将信标添加到信标仪表板时，可以仅将附件添加到添加了信标的项目。我可以配置命名空间、类型和数据。
今天我不得不配置另一个项目，令我惊讶的是，当我在附件选项卡中时，我可以选择一个不同的项目来添加该附件，并且命名空间不再是可编辑的（默认情况下给出，它类似于项目编号）。
这是否意味着我可以拥有一个 "My beacons global project" 然后配置其他项目的附件？我已经进行了测试，附件已按配置交付给其他项目。
同时发生了什么变化，还是我从一开始就错过了这个？
谢谢你的时间。
By default, your project's namespace visibility is set to UNLISTED, so its attachments are served only to your project, not to other developers' projects.
A single beacon can support multiple attachments in different namespaces, added by different projects using the Proximity Beacon API's IAM roles. Each project controls the visibility of its namespace, so it is possible for a single beacon to support a mixture of public and unlisted attachments.